Public report of airyhq/airy, published 17 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 17 November 2026, 05:57 UTC · Survey ID cd_828509d13c5645a88ac20b8dd8f62f1f
airyhq/airy
Measured 17 November 2026, 05:55 UTC, at code version 4599f2b
Bus factor is not measured: No living knowledge left to concentrate.
Supply-chain provenance & signing is not measured: Supply-chain provenance is not scored (this pipeline releases no artifact), but its build steps or GitHub Actions workflows have integrity defects, or nothing watches its dependency set for published advisories.
CAI scoreAt risk
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 54,176 lines of product code in 81 projects, tests not counted · Estimated rebuild effort: about 0.3 person-years · Weakest lens: Production Readiness, 24.9
Findings by how serious they are
263 critical996 serious664 minor
11 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
17 November 2026, 05:55 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.
The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
81of 81 dimensions measured by tools.
1859of 1923 findings point to an exact file and line, so you can open each one in the code. The other 64 concern the repository as a whole, such as missing documentation.
81dimensions across 7 lenses, read from 54,176 lines of product code in 81 projects.
airyhq/airy is rated At risk because critical security findings are open. Its score is held back because three passwords or keys sit in the current code and it has uses of packages that aren't listed. It scores 35.9 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 24.9, is the weakest lens and counts most in the score. The best first step is replacing the three exposed passwords or keys and switching the old ones off, worth about 9.3 points. Pinning the dependencies to tagged releases comes next, worth about 8.1 points. Raising Production Readiness to 70 would lift the score to about 45.0.
Sixty-eight settings leave the servers or containers unsafe. Sixty-six known security holes in the packages the code depends on can be used by attackers, and forty controls can't be used without a mouse. Correcting the unsafe settings, updating the vulnerable packages and making the controls work with a keyboard would close these risks. Pinning each tool to an exact version would fix the four pipeline tools referenced by a changeable name, and the 11 passwords or keys in the code's history and the three passwords or keys in the code need replacing, with the old ones switched off. The 25 buttons or links with no name need a name, even when they only show an icon.
The product code is 54,176 lines, about €48,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 24.9 to 70, the lowest score rated Strong, the score would rise from 35.9 to about 45.0.
Code composition: what the lines of code are
Product code 87%Tests 13%
Rebuild cost: about €48,000 · Estimate
Cost to rebuild
€16,000 to €80,000, for 265 to 840 hours of work, about 0.3 person-years for one engineer
Difficulty of the problem
Low, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 36. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 54,176 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 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED.
Raises the score by about 9.3 points · Low effort · REDACTED Scanning
2
Resolve the 4 Dependency pinned to a stale untagged commit finding(s) in Dependency Hygiene.
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 €48,000 to build again, about 0.3 person-years of work. Its weakest lens is Production Readiness, at 24.9 (Critical). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 3 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 9.3 points for low effort, because it clears the 3 REDACTED Scanning findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
Architecture — 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.
384 modules, with 260 dependencies between them. 3 loops run through 7 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 344 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.
cli/pkg/workspace uses cli/pkg/workspace/template, so a change to cli/pkg/workspace/template can break cli/pkg/workspace, while a change to cli/pkg/workspace can't break cli/pkg/workspace/template.
Position
Below the diagonal: cli/pkg/workspace uses a module listed above it, which is the healthy direction.
co.airy.core.chat_plugin uses co.airy.kafka.streams, so a change to co.airy.kafka.streams can break co.airy.core.chat_plugin, while a change to co.airy.core.chat_plugin can't break co.airy.kafka.streams.
Position
Below the diagonal: co.airy.core.chat_plugin uses a module listed above it, which is the healthy direction.
co.airy.model.channel.dto uses co.airy.model.metadata.dto, so a change to co.airy.model.metadata.dto can break co.airy.model.channel.dto, while a change to co.airy.model.channel.dto can't break co.airy.model.metadata.dto.
Position
Below the diagonal: co.airy.model.channel.dto uses a module listed above it, which is the healthy direction.
co.airy.model.message.dto uses co.airy.model.metadata.dto, so a change to co.airy.model.metadata.dto can break co.airy.model.message.dto, while a change to co.airy.model.message.dto can't break co.airy.model.metadata.dto.
Position
Below the diagonal: co.airy.model.message.dto uses a module listed above it, which is the healthy direction.
15→20 co.airy.spring.auth.session uses co.airy.spring.authpart of a loop✕
Connections
2 pairs of types, where a type in co.airy.spring.auth.session uses a type in co.airy.spring.auth.
co.airy.spring.auth.session uses co.airy.spring.auth, so a change to co.airy.spring.auth can break co.airy.spring.auth.session, while a change to co.airy.spring.auth.session can't break co.airy.spring.auth.
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.
lib.typescript.model.Message uses lib.typescript.render.providers.meta.MetaModel, so a change to lib.typescript.render.providers.meta.MetaModel can break lib.typescript.model.Message, while a change to lib.typescript.model.Message can't break lib.typescript.render.providers.meta.MetaModel.
Position
Below the diagonal: lib.typescript.model.Message uses a module listed above it, which is the healthy direction.
cli/pkg/providers uses cli/pkg/console, so a change to cli/pkg/console can break cli/pkg/providers, while a change to cli/pkg/providers can't break cli/pkg/console.
Position
Below the diagonal: cli/pkg/providers uses a module listed above it, which is the healthy direction.
cli/pkg/providers uses cli/pkg/workspace/template, so a change to cli/pkg/workspace/template can break cli/pkg/providers, while a change to cli/pkg/providers can't break cli/pkg/workspace/template.
Position
Below the diagonal: cli/pkg/providers uses a module listed above it, which is the healthy direction.
cli/pkg/providers uses cli/pkg/workspace, so a change to cli/pkg/workspace can break cli/pkg/providers, while a change to cli/pkg/providers can't break cli/pkg/workspace.
Position
Below the diagonal: cli/pkg/providers uses a module listed above it, which is the healthy direction.
co.airy.core.sources.api uses co.airy.kafka.streams, so a change to co.airy.kafka.streams can break co.airy.core.sources.api, while a change to co.airy.core.sources.api can't break co.airy.kafka.streams.
Position
Below the diagonal: co.airy.core.sources.api uses a module listed above it, which is the healthy direction.
co.airy.core.sources.api uses co.airy.model.metadata.dto, so a change to co.airy.model.metadata.dto can break co.airy.core.sources.api, while a change to co.airy.core.sources.api can't break co.airy.model.metadata.dto.
Position
Below the diagonal: co.airy.core.sources.api uses a module listed above it, which is the healthy direction.
co.airy.core.sources.api uses co.airy.model.channel.dto, so a change to co.airy.model.channel.dto can break co.airy.core.sources.api, while a change to co.airy.core.sources.api can't break co.airy.model.channel.dto.
Position
Below the diagonal: co.airy.core.sources.api uses a module listed above it, which is the healthy direction.
co.airy.model.channel uses co.airy.model.channel.dto, so a change to co.airy.model.channel.dto can break co.airy.model.channel, while a change to co.airy.model.channel can't break co.airy.model.channel.dto.
Position
Below the diagonal: co.airy.model.channel uses a module listed above it, which is the healthy direction.
co.airy.spring.auth uses co.airy.spring.auth.session, so a change to co.airy.spring.auth.session can break co.airy.spring.auth, while a change to co.airy.spring.auth can't break co.airy.spring.auth.session.
Position
Below the diagonal: co.airy.spring.auth uses a module listed above it, which is the healthy direction.
lib.typescript.model.Conversation uses lib.typescript.model.Message, so a change to lib.typescript.model.Message can break lib.typescript.model.Conversation, while a change to lib.typescript.model.Conversation can't break lib.typescript.model.Message.
Position
Below the diagonal: lib.typescript.model.Conversation uses a module listed above it, which is the healthy direction.
cli/pkg/providers/aws uses cli/pkg/console, so a change to cli/pkg/console can break cli/pkg/providers/aws, while a change to cli/pkg/providers/aws can't break cli/pkg/console.
Position
Below the diagonal: cli/pkg/providers/aws uses a module listed above it, which is the healthy direction.
cli/pkg/providers/aws uses cli/pkg/workspace/template, so a change to cli/pkg/workspace/template can break cli/pkg/providers/aws, while a change to cli/pkg/providers/aws can't break cli/pkg/workspace/template.
Position
Below the diagonal: cli/pkg/providers/aws uses a module listed above it, which is the healthy direction.
cli/pkg/providers/aws uses cli/pkg/workspace, so a change to cli/pkg/workspace can break cli/pkg/providers/aws, while a change to cli/pkg/providers/aws can't break cli/pkg/workspace.
Position
Below the diagonal: cli/pkg/providers/aws uses a module listed above it, which is the healthy direction.
cli/pkg/providers/aws uses cli/pkg/providers, so a change to cli/pkg/providers can break cli/pkg/providers/aws, while a change to cli/pkg/providers/aws can't break cli/pkg/providers.
Position
Below the diagonal: cli/pkg/providers/aws uses a module listed above it, which is the healthy direction.
cli/pkg/providers/gcp uses cli/pkg/console, so a change to cli/pkg/console can break cli/pkg/providers/gcp, while a change to cli/pkg/providers/gcp can't break cli/pkg/console.
Position
Below the diagonal: cli/pkg/providers/gcp uses a module listed above it, which is the healthy direction.
cli/pkg/providers/gcp uses cli/pkg/workspace/template, so a change to cli/pkg/workspace/template can break cli/pkg/providers/gcp, while a change to cli/pkg/providers/gcp can't break cli/pkg/workspace/template.
Position
Below the diagonal: cli/pkg/providers/gcp uses a module listed above it, which is the healthy direction.
cli/pkg/providers/gcp uses cli/pkg/workspace, so a change to cli/pkg/workspace can break cli/pkg/providers/gcp, while a change to cli/pkg/providers/gcp can't break cli/pkg/workspace.
Position
Below the diagonal: cli/pkg/providers/gcp uses a module listed above it, which is the healthy direction.
cli/pkg/providers/gcp uses cli/pkg/providers, so a change to cli/pkg/providers can break cli/pkg/providers/gcp, while a change to cli/pkg/providers/gcp can't break cli/pkg/providers.
Position
Below the diagonal: cli/pkg/providers/gcp uses a module listed above it, which is the healthy direction.
cli/pkg/providers/minikube uses cli/pkg/console, so a change to cli/pkg/console can break cli/pkg/providers/minikube, while a change to cli/pkg/providers/minikube can't break cli/pkg/console.
Position
Below the diagonal: cli/pkg/providers/minikube uses a module listed above it, which is the healthy direction.
cli/pkg/providers/minikube uses cli/pkg/workspace/template, so a change to cli/pkg/workspace/template can break cli/pkg/providers/minikube, while a change to cli/pkg/providers/minikube can't break cli/pkg/workspace/template.
Position
Below the diagonal: cli/pkg/providers/minikube uses a module listed above it, which is the healthy direction.
cli/pkg/providers/minikube uses cli/pkg/workspace, so a change to cli/pkg/workspace can break cli/pkg/providers/minikube, while a change to cli/pkg/providers/minikube can't break cli/pkg/workspace.
Position
Below the diagonal: cli/pkg/providers/minikube uses a module listed above it, which is the healthy direction.
cli/pkg/providers/minikube uses cli/pkg/providers, so a change to cli/pkg/providers can break cli/pkg/providers/minikube, while a change to cli/pkg/providers/minikube can't break cli/pkg/providers.
Position
Below the diagonal: cli/pkg/providers/minikube uses a module listed above it, which is the healthy direction.
co.airy.core.config uses co.airy.spring.auth, so a change to co.airy.spring.auth can break co.airy.core.config, while a change to co.airy.core.config can't break co.airy.spring.auth.
Position
Below the diagonal: co.airy.core.config uses a module listed above it, which is the healthy direction.
co.airy.model.conversation uses co.airy.model.metadata.dto, so a change to co.airy.model.metadata.dto can break co.airy.model.conversation, while a change to co.airy.model.conversation can't break co.airy.model.metadata.dto.
Position
Below the diagonal: co.airy.model.conversation uses a module listed above it, which is the healthy direction.
co.airy.model.conversation uses co.airy.model.channel.dto, so a change to co.airy.model.channel.dto can break co.airy.model.conversation, while a change to co.airy.model.conversation can't break co.airy.model.channel.dto.
Position
Below the diagonal: co.airy.model.conversation uses a module listed above it, which is the healthy direction.
co.airy.model.conversation uses co.airy.model.message.dto, so a change to co.airy.model.message.dto can break co.airy.model.conversation, while a change to co.airy.model.conversation can't break co.airy.model.message.dto.
Position
Below the diagonal: co.airy.model.conversation uses a module listed above it, which is the healthy direction.
co.airy.model.conversation uses co.airy.model.channel, so a change to co.airy.model.channel can break co.airy.model.conversation, while a change to co.airy.model.conversation can't break co.airy.model.channel.
Position
Below the diagonal: co.airy.model.conversation uses a module listed above it, which is the healthy direction.
co.airy.spring.web.filters uses co.airy.spring.auth.session, so a change to co.airy.spring.auth.session can break co.airy.spring.web.filters, while a change to co.airy.spring.web.filters can't break co.airy.spring.auth.session.
Position
Below the diagonal: co.airy.spring.web.filters uses a module listed above it, which is the healthy direction.
co.airy.spring.web.filters uses co.airy.spring.auth, so a change to co.airy.spring.auth can break co.airy.spring.web.filters, while a change to co.airy.spring.web.filters can't break co.airy.spring.auth.
Position
Below the diagonal: co.airy.spring.web.filters uses a module listed above it, which is the healthy direction.
co.airy.core.communication.dto uses co.airy.model.metadata.dto, so a change to co.airy.model.metadata.dto can break co.airy.core.communication.dto, while a change to co.airy.core.communication.dto can't break co.airy.model.metadata.dto.
Position
Below the diagonal: co.airy.core.communication.dto uses a module listed above it, which is the healthy direction.
co.airy.core.communication.dto uses co.airy.model.message.dto, so a change to co.airy.model.message.dto can break co.airy.core.communication.dto, while a change to co.airy.core.communication.dto can't break co.airy.model.message.dto.
Position
Below the diagonal: co.airy.core.communication.dto uses a module listed above it, which is the healthy direction.
co.airy.core.communication.dto uses co.airy.model.conversation, so a change to co.airy.model.conversation can break co.airy.core.communication.dto, while a change to co.airy.core.communication.dto can't break co.airy.model.conversation.
Position
Below the diagonal: co.airy.core.communication.dto uses a module listed above it, which is the healthy direction.
co.airy.core.communication.payload uses co.airy.model.message.dto, so a change to co.airy.model.message.dto can break co.airy.core.communication.payload, while a change to co.airy.core.communication.payload can't break co.airy.model.message.dto.
Position
Below the diagonal: co.airy.core.communication.payload uses a module listed above it, which is the healthy direction.
co.airy.core.communication.payload uses co.airy.model.channel, so a change to co.airy.model.channel can break co.airy.core.communication.payload, while a change to co.airy.core.communication.payload can't break co.airy.model.channel.
Position
Below the diagonal: co.airy.core.communication.payload uses a module listed above it, which is the healthy direction.
co.airy.core.communication.payload uses co.airy.model.conversation, so a change to co.airy.model.conversation can break co.airy.core.communication.payload, while a change to co.airy.core.communication.payload can't break co.airy.model.conversation.
Position
Below the diagonal: co.airy.core.communication.payload uses a module listed above it, which is the healthy direction.
co.airy.core.sources.facebook uses co.airy.kafka.streams, so a change to co.airy.kafka.streams can break co.airy.core.sources.facebook, while a change to co.airy.core.sources.facebook can't break co.airy.kafka.streams.
Position
Below the diagonal: co.airy.core.sources.facebook uses a module listed above it, which is the healthy direction.
co.airy.core.sources.facebook uses co.airy.tracking, so a change to co.airy.tracking can break co.airy.core.sources.facebook, while a change to co.airy.core.sources.facebook can't break co.airy.tracking.
Position
Below the diagonal: co.airy.core.sources.facebook uses a module listed above it, which is the healthy direction.
co.airy.core.sources.facebook uses co.airy.model.channel.dto, so a change to co.airy.model.channel.dto can break co.airy.core.sources.facebook, while a change to co.airy.core.sources.facebook can't break co.airy.model.channel.dto.
Position
Below the diagonal: co.airy.core.sources.facebook uses a module listed above it, which is the healthy direction.
co.airy.core.sources.facebook uses co.airy.spring.auth, so a change to co.airy.spring.auth can break co.airy.core.sources.facebook, while a change to co.airy.core.sources.facebook can't break co.airy.spring.auth.
Position
Below the diagonal: co.airy.core.sources.facebook uses a module listed above it, which is the healthy direction.
co.airy.core.sources.facebook uses co.airy.spring.web.filters, so a change to co.airy.spring.web.filters can break co.airy.core.sources.facebook, while a change to co.airy.core.sources.facebook can't break co.airy.spring.web.filters.
Position
Below the diagonal: co.airy.core.sources.facebook uses a module listed above it, which is the healthy direction.
co.airy.core.sources.google uses co.airy.kafka.streams, so a change to co.airy.kafka.streams can break co.airy.core.sources.google, while a change to co.airy.core.sources.google can't break co.airy.kafka.streams.
Position
Below the diagonal: co.airy.core.sources.google uses a module listed above it, which is the healthy direction.
co.airy.core.sources.google uses co.airy.tracking, so a change to co.airy.tracking can break co.airy.core.sources.google, while a change to co.airy.core.sources.google can't break co.airy.tracking.
Position
Below the diagonal: co.airy.core.sources.google uses a module listed above it, which is the healthy direction.
co.airy.core.sources.google uses co.airy.model.channel.dto, so a change to co.airy.model.channel.dto can break co.airy.core.sources.google, while a change to co.airy.core.sources.google can't break co.airy.model.channel.dto.
Position
Below the diagonal: co.airy.core.sources.google uses a module listed above it, which is the healthy direction.
co.airy.core.sources.google uses co.airy.spring.auth, so a change to co.airy.spring.auth can break co.airy.core.sources.google, while a change to co.airy.core.sources.google can't break co.airy.spring.auth.
Position
Below the diagonal: co.airy.core.sources.google uses a module listed above it, which is the healthy direction.
co.airy.core.sources.google uses co.airy.spring.web.filters, so a change to co.airy.spring.web.filters can break co.airy.core.sources.google, while a change to co.airy.core.sources.google can't break co.airy.spring.web.filters.
Position
Below the diagonal: co.airy.core.sources.google uses a module listed above it, which is the healthy direction.
co.airy.core.sources.twilio uses co.airy.kafka.streams, so a change to co.airy.kafka.streams can break co.airy.core.sources.twilio, while a change to co.airy.core.sources.twilio can't break co.airy.kafka.streams.
Position
Below the diagonal: co.airy.core.sources.twilio uses a module listed above it, which is the healthy direction.
co.airy.core.sources.twilio uses co.airy.tracking, so a change to co.airy.tracking can break co.airy.core.sources.twilio, while a change to co.airy.core.sources.twilio can't break co.airy.tracking.
Position
Below the diagonal: co.airy.core.sources.twilio uses a module listed above it, which is the healthy direction.
co.airy.core.sources.twilio uses co.airy.model.channel.dto, so a change to co.airy.model.channel.dto can break co.airy.core.sources.twilio, while a change to co.airy.core.sources.twilio can't break co.airy.model.channel.dto.
Position
Below the diagonal: co.airy.core.sources.twilio uses a module listed above it, which is the healthy direction.
co.airy.core.sources.twilio uses co.airy.spring.auth, so a change to co.airy.spring.auth can break co.airy.core.sources.twilio, while a change to co.airy.core.sources.twilio can't break co.airy.spring.auth.
Position
Below the diagonal: co.airy.core.sources.twilio uses a module listed above it, which is the healthy direction.
co.airy.core.sources.twilio uses co.airy.spring.web.filters, so a change to co.airy.spring.web.filters can break co.airy.core.sources.twilio, while a change to co.airy.core.sources.twilio can't break co.airy.spring.web.filters.
Position
Below the diagonal: co.airy.core.sources.twilio uses a module listed above it, which is the healthy direction.
co.airy.core.sources.viber uses co.airy.kafka.streams, so a change to co.airy.kafka.streams can break co.airy.core.sources.viber, while a change to co.airy.core.sources.viber can't break co.airy.kafka.streams.
Position
Below the diagonal: co.airy.core.sources.viber uses a module listed above it, which is the healthy direction.
co.airy.core.sources.viber uses co.airy.tracking, so a change to co.airy.tracking can break co.airy.core.sources.viber, while a change to co.airy.core.sources.viber can't break co.airy.tracking.
Position
Below the diagonal: co.airy.core.sources.viber uses a module listed above it, which is the healthy direction.
co.airy.core.sources.viber uses co.airy.model.channel.dto, so a change to co.airy.model.channel.dto can break co.airy.core.sources.viber, while a change to co.airy.core.sources.viber can't break co.airy.model.channel.dto.
Position
Below the diagonal: co.airy.core.sources.viber uses a module listed above it, which is the healthy direction.
co.airy.core.sources.viber uses co.airy.spring.auth, so a change to co.airy.spring.auth can break co.airy.core.sources.viber, while a change to co.airy.core.sources.viber can't break co.airy.spring.auth.
Position
Below the diagonal: co.airy.core.sources.viber uses a module listed above it, which is the healthy direction.
co.airy.core.sources.viber uses co.airy.spring.web.filters, so a change to co.airy.spring.web.filters can break co.airy.core.sources.viber, while a change to co.airy.core.sources.viber can't break co.airy.spring.web.filters.
Position
Below the diagonal: co.airy.core.sources.viber uses a module listed above it, which is the healthy direction.
co.airy.core.sources.whatsapp uses co.airy.kafka.streams, so a change to co.airy.kafka.streams can break co.airy.core.sources.whatsapp, while a change to co.airy.core.sources.whatsapp can't break co.airy.kafka.streams.
Position
Below the diagonal: co.airy.core.sources.whatsapp uses a module listed above it, which is the healthy direction.
co.airy.core.sources.whatsapp uses co.airy.tracking, so a change to co.airy.tracking can break co.airy.core.sources.whatsapp, while a change to co.airy.core.sources.whatsapp can't break co.airy.tracking.
Position
Below the diagonal: co.airy.core.sources.whatsapp uses a module listed above it, which is the healthy direction.
co.airy.core.sources.whatsapp uses co.airy.model.channel.dto, so a change to co.airy.model.channel.dto can break co.airy.core.sources.whatsapp, while a change to co.airy.core.sources.whatsapp can't break co.airy.model.channel.dto.
Position
Below the diagonal: co.airy.core.sources.whatsapp uses a module listed above it, which is the healthy direction.
co.airy.core.sources.whatsapp uses co.airy.spring.auth, so a change to co.airy.spring.auth can break co.airy.core.sources.whatsapp, while a change to co.airy.core.sources.whatsapp can't break co.airy.spring.auth.
Position
Below the diagonal: co.airy.core.sources.whatsapp uses a module listed above it, which is the healthy direction.
co.airy.core.sources.whatsapp uses co.airy.spring.web.filters, so a change to co.airy.spring.web.filters can break co.airy.core.sources.whatsapp, while a change to co.airy.core.sources.whatsapp can't break co.airy.spring.web.filters.
Position
Below the diagonal: co.airy.core.sources.whatsapp uses a module listed above it, which is the healthy direction.
co.airy.model.contact uses co.airy.model.metadata.dto, so a change to co.airy.model.metadata.dto can break co.airy.model.contact, while a change to co.airy.model.contact can't break co.airy.model.metadata.dto.
Position
Below the diagonal: co.airy.model.contact uses a module listed above it, which is the healthy direction.
co.airy.model.contact uses co.airy.model.conversation, so a change to co.airy.model.conversation can break co.airy.model.contact, while a change to co.airy.model.contact can't break co.airy.model.conversation.
Position
Below the diagonal: co.airy.model.contact uses a module listed above it, which is the healthy direction.
co.airy.model.event.payload uses co.airy.model.metadata.dto, so a change to co.airy.model.metadata.dto can break co.airy.model.event.payload, while a change to co.airy.model.event.payload can't break co.airy.model.metadata.dto.
Position
Below the diagonal: co.airy.model.event.payload uses a module listed above it, which is the healthy direction.
co.airy.model.event.payload uses co.airy.model.message.dto, so a change to co.airy.model.message.dto can break co.airy.model.event.payload, while a change to co.airy.model.event.payload can't break co.airy.model.message.dto.
Position
Below the diagonal: co.airy.model.event.payload uses a module listed above it, which is the healthy direction.
co.airy.model.event.payload uses co.airy.model.channel, so a change to co.airy.model.channel can break co.airy.model.event.payload, while a change to co.airy.model.event.payload can't break co.airy.model.channel.
Position
Below the diagonal: co.airy.model.event.payload uses a module listed above it, which is the healthy direction.
co.airy.model.event.payload uses co.airy.model.conversation, so a change to co.airy.model.conversation can break co.airy.model.event.payload, while a change to co.airy.model.event.payload can't break co.airy.model.conversation.
Position
Below the diagonal: co.airy.model.event.payload uses a module listed above it, which is the healthy direction.
co.airy.core.admin.payload uses co.airy.model.channel, so a change to co.airy.model.channel can break co.airy.core.admin.payload, while a change to co.airy.core.admin.payload can't break co.airy.model.channel.
Position
Below the diagonal: co.airy.core.admin.payload uses a module listed above it, which is the healthy direction.
co.airy.core.admin.payload uses co.airy.model.event.payload, so a change to co.airy.model.event.payload can break co.airy.core.admin.payload, while a change to co.airy.core.admin.payload can't break co.airy.model.event.payload.
Position
Below the diagonal: co.airy.core.admin.payload uses a module listed above it, which is the healthy direction.
co.airy.core.communication uses co.airy.kafka.streams, so a change to co.airy.kafka.streams can break co.airy.core.communication, while a change to co.airy.core.communication can't break co.airy.kafka.streams.
Position
Below the diagonal: co.airy.core.communication uses a module listed above it, which is the healthy direction.
co.airy.core.communication uses co.airy.model.metadata.dto, so a change to co.airy.model.metadata.dto can break co.airy.core.communication, while a change to co.airy.core.communication can't break co.airy.model.metadata.dto.
Position
Below the diagonal: co.airy.core.communication uses a module listed above it, which is the healthy direction.
co.airy.core.communication uses co.airy.model.message.dto, so a change to co.airy.model.message.dto can break co.airy.core.communication, while a change to co.airy.core.communication can't break co.airy.model.message.dto.
Position
Below the diagonal: co.airy.core.communication uses a module listed above it, which is the healthy direction.
co.airy.core.communication uses co.airy.spring.auth, so a change to co.airy.spring.auth can break co.airy.core.communication, while a change to co.airy.core.communication can't break co.airy.spring.auth.
Position
Below the diagonal: co.airy.core.communication uses a module listed above it, which is the healthy direction.
co.airy.core.communication uses co.airy.model.conversation, so a change to co.airy.model.conversation can break co.airy.core.communication, while a change to co.airy.core.communication can't break co.airy.model.conversation.
Position
Below the diagonal: co.airy.core.communication uses a module listed above it, which is the healthy direction.
co.airy.core.communication uses co.airy.core.communication.dto, so a change to co.airy.core.communication.dto can break co.airy.core.communication, while a change to co.airy.core.communication can't break co.airy.core.communication.dto.
Position
Below the diagonal: co.airy.core.communication uses a module listed above it, which is the healthy direction.
co.airy.core.communication uses co.airy.core.communication.payload, so a change to co.airy.core.communication.payload can break co.airy.core.communication, while a change to co.airy.core.communication can't break co.airy.core.communication.payload.
Position
Below the diagonal: co.airy.core.communication uses a module listed above it, which is the healthy direction.
co.airy.core.contacts uses co.airy.kafka.streams, so a change to co.airy.kafka.streams can break co.airy.core.contacts, while a change to co.airy.core.contacts can't break co.airy.kafka.streams.
Position
Below the diagonal: co.airy.core.contacts uses a module listed above it, which is the healthy direction.
co.airy.core.contacts uses co.airy.model.metadata.dto, so a change to co.airy.model.metadata.dto can break co.airy.core.contacts, while a change to co.airy.core.contacts can't break co.airy.model.metadata.dto.
Position
Below the diagonal: co.airy.core.contacts uses a module listed above it, which is the healthy direction.
co.airy.core.contacts uses co.airy.model.conversation, so a change to co.airy.model.conversation can break co.airy.core.contacts, while a change to co.airy.core.contacts can't break co.airy.model.conversation.
Position
Below the diagonal: co.airy.core.contacts uses a module listed above it, which is the healthy direction.
co.airy.core.contacts uses co.airy.model.contact, so a change to co.airy.model.contact can break co.airy.core.contacts, while a change to co.airy.core.contacts can't break co.airy.model.contact.
Position
Below the diagonal: co.airy.core.contacts uses a module listed above it, which is the healthy direction.
co.airy.core.admin uses co.airy.kafka.streams, so a change to co.airy.kafka.streams can break co.airy.core.admin, while a change to co.airy.core.admin can't break co.airy.kafka.streams.
Position
Below the diagonal: co.airy.core.admin uses a module listed above it, which is the healthy direction.
co.airy.core.admin uses co.airy.model.metadata.dto, so a change to co.airy.model.metadata.dto can break co.airy.core.admin, while a change to co.airy.core.admin can't break co.airy.model.metadata.dto.
Position
Below the diagonal: co.airy.core.admin uses a module listed above it, which is the healthy direction.
co.airy.core.admin uses co.airy.tracking, so a change to co.airy.tracking can break co.airy.core.admin, while a change to co.airy.core.admin can't break co.airy.tracking.
Position
Below the diagonal: co.airy.core.admin uses a module listed above it, which is the healthy direction.
co.airy.core.admin uses co.airy.model.channel.dto, so a change to co.airy.model.channel.dto can break co.airy.core.admin, while a change to co.airy.core.admin can't break co.airy.model.channel.dto.
Position
Below the diagonal: co.airy.core.admin uses a module listed above it, which is the healthy direction.
co.airy.core.admin uses co.airy.core.config, so a change to co.airy.core.config can break co.airy.core.admin, while a change to co.airy.core.admin can't break co.airy.core.config.
Position
Below the diagonal: co.airy.core.admin uses a module listed above it, which is the healthy direction.
co.airy.core.admin uses co.airy.core.admin.payload, so a change to co.airy.core.admin.payload can break co.airy.core.admin, while a change to co.airy.core.admin can't break co.airy.core.admin.payload.
Position
Below the diagonal: co.airy.core.admin uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 38.1 · Weak · gated by R10, R7 ·
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
A02:2025 — Security Misconfiguration
582
High / Critical
A03:2025 — Software Supply Chain Failures
115
High / Critical
A05:2025 — Injection
59
High / Critical
A07:2025 — Authentication Failures
15
High / Critical
Roadmap
Top priorities: Resolve the 51 No assertions finding(s) in Test Quality — start with ConversationsListTest.java (12), MessagesTest.java (6), AuthenticationTest.java (4); Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED; Resolve the 4 Dependency pinned to a stale untagged commit finding(s) in Dependency Hygiene.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED.
Resolve the 51 No assertions finding(s) in Test Quality — start with ConversationsListTest.java (12), MessagesTest.java (6), AuthenticationTest.java (4).
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 — 263
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 — 996
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 — 664
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 11
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 81 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 — 81 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, 1859 of 1923 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: this repository's production source spans .ts, .tsx, .java, and our analyzer cannot run the .java test suite(s) — so no coverage was collected for the repository as a whole. The JavaScript/TypeScript half did build and run, and its own line coverage came back at 59.9% — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — coverage is excluded from the score rather than counted as a near-zero.
D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 117 test(s) behind this row are the ones the code-model census could read, and this repository also carries at least 13 test source file(s) (.ts, .tsx) that it cannot: it reads the test types the .java frontend declared, so a suite in any other language is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT SCORED: this repository's production source includes .java, and the built-in reliability runner cannot re-run the .java test suite(s) — so reliability was not measured for the repository as a whole. The JavaScript/TypeScript (jest via `yarn install --frozen-lockfile --ignore-scripts` in the repository root (2 tests)): measured (0 flaky) suite(s) did re-run, and came back with 0 flaky across 1 measured tier(s) — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — test reliability is excluded from the score rather than counted.
D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Go module (REDACTED/go.sum), but the licence verdict published here was taken over its npm package dependencies. Nothing was read about its Go dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. All 260 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains — nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness). Counted over 236 of the 993 production source files in this repository: 733 are under the ~2,400-byte size floor this dimension measures over, and the remaining 24 have no attributable history left to measure.
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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. D24 compares a comment's words with the identifiers, literals and constructs of the code it annotates, using English function-word and rationale lexicons. Comments in another script or language were left unread rather than counted as clean.
D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
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. `frontend/control-center/src/pages/LLMConsumers/LLMConsumerItem/index.tsx`, `lib/typescript/httpclient/src/client.ts` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
D41 Kernel & Syscall Confinement — 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. Backend/components/chat-plugin/helm/templates/backend/deployment.yaml:2, REDACTED:2, REDACTED:2, backend/components/contacts/helm/templates/deployment.yaml:2, REDACTED:2, REDACTED:91, REDACTED:2, REDACTED:2, REDACTED:2, REDACTED:86 and 42 more did not read as a pod spec (a templated manifest such as Helm's that is not YAML until rendered, or a workload whose pod spec this check does not locate), so the seccomp/AppArmor profile in force there was not judged and no row about them can appear on this card.
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. 1 further occurrence(s) are not listed individually; the score already reflects all 41.
AC4 Keyboard semantics — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 25 further occurrence(s) are not listed individually; the score already reflects all 65.
AC6 Visual & motion safety — 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.
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. User interface: 247 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. Boot: crawled PUBLIC routes only — add a Playwright storageState (e.g. playwright/.auth/user.json) or a test auth-setup to crawl authenticated screens rendered 0/1 surface(s) × 2 renders render failed for http://127.0.0.1:32768: page.addStyleTag: Refused to apply inline style because it violates the following Content Security Policy directive: "default-src 'none'". Either the 'unsafe-in ran the repo's cypress suite against the booted app but captured no surfaces (suite failed to install/run, or visited no pages) — see runtime diagnostics.
C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
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. 111 further occurrence(s) are not listed individually; the score already reflects all 151.
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. 15 further occurrence(s) are not listed individually; the score already reflects all 55.
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. 367 further occurrence(s) are not listed individually; the score already reflects all 407.
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. 270 further occurrence(s) are not listed individually; the score already reflects all 310.
X1 Async correctness — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X12 Unreachable branch — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X26 Unsynchronised callback handoff — 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 — 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.
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. 1 further occurrence(s) are not listed individually; the score already reflects all 41.
Repo exclusion declarations: 11 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.
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.
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.
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.
D40 Network Egress Confinement: Egress confinement is read from committed Kubernetes manifests — a policy applied out-of-band (cluster-default deny, a service mesh, or a cloud firewall/security group off-repo) is invisible, and a present NetworkPolicy is declared config, not proof the cluster admission-controller actually enforces it at runtime.
D41 Kernel & Syscall Confinement: Syscall/MAC confinement is read from committed manifests — a profile applied by a cluster-wide PodSecurity default or a mutating webhook off-repo isn't seen, and a declared seccomp/AppArmor profile is config presence, not proof the node's kernel actually loaded and enforced it.
D42 Runtime Threat Enforcement: Runtime enforcement is read from committed policy files — a Tetragon/Falco/Kyverno stack installed cluster-wide (Helm release, platform add-on) with no in-repo trace can't be credited, and a committed policy is declared intent, not proof the engine is running and blocking in the live cluster.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (REDACTED, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
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.
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.
61 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was index.ConnectorConfig at 51. A further 3 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 index.getChannelAvatar at 62 — they are counted neither in the figure above nor in this dimension's score. 3 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: frontend/control-center/src/components/ChannelAvatar/index.tsx (index.getChannelAvatar at 62), frontend/control-center/src/pages/Connectors/ConfigureConnector/SetConfigInputs/SetConfigInputs.tsx (SetConfigInputs.SetConfigInputs at 24), lib/typescript/components/cta/SmartButton/index.tsx (index.SmartButton at 19). 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.
+ 54 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 61 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with index.ConnectorConfig (cyclomatic 51), InputOptions.InputOptions (cyclomatic 50), index.ContactDetails (cyclomatic 48). — 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 61 together lifts Cyclomatic Complexity from 6.5 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
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.
+ 57 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 64 bodies over 15 down to 15 or less in Cognitive Complexity — start with MetaRender.metaOutbound (cognitive 56), index.ContactDetails (cognitive 49), index.Catalog (cognitive 47). — 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 64 together lifts Cognitive Complexity from 6.4 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes5.7 / 10Adequate✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 47 FunctionTooLong finding(s) in God Classes — start with REDACTED (29), CustomiseSection.tsx, Popup.tsx. — One of this dimension's main actionable groups (47 warning-level).
Resolve the 1 MethodTooLong finding(s) in God Classes — start with REDACTED. — One of this dimension's main actionable groups (1 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.
64 duplicated block group(s) detected. 4.3 % of the production lines (2,351 of 54,176) are in a reported copy. A further 42 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, .ts (58% 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 (25 corresponding lines) · ×3backend/components/contacts/src/main/java/co/airy/core/contacts/ContactsController.java:46
+ 67 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 7 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with ConversationsController.java (2), Stores.java, WebhookController.java. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 5 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with ChannelsController.java, Jwt.java, ConversationsController.java. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 4 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with Jwt.java, Connector.java, Component.java. — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling9.7 / 10Stronggated by 3 serious findings✓ 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.
81 production modules (npm+Go+Bazel), 0 dependency cycle(s), 1 unstable depended-on module(s). Read from the build's own module declarations; 2 module(s) off the main sequence, with abstractness counted on 8 of the 81 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
Off the main sequence: github.com/airyhq/airy/infrastructure/lib/go/k8s/util · ×2
Unstable project //backend/model/event:event
What to do
Resolve the 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 Unstable project //backend/model/event finding(s) in Coupling. — One of this dimension's main actionable groups (1 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.
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
0 skipped, 51 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 117 tests. Measured on the .java suite only — at least 13 test source file(s) (.ts, .tsx) went unread, so its test quality is unmeasured and is not in these counts.
No assertions: canListChannels · ×51backend/components/admin/src/test/java/co/airy/core/admin/ChannelsControllerTest.java:82
What to do
Resolve the 51 No assertions finding(s) in Test Quality — start with ConversationsListTest.java (12), MessagesTest.java (6), AuthenticationTest.java (4). — One of this dimension's main actionable groups (51 warning-level).
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.
43 outdated, 2 author-deprecated direct Go module(s), 4 pinning or checksum defect(s). 60 of 60 direct requirement(s) were graded against proxy.golang.org (0 not served there, 1 publishing no tagged release to be behind). Whether any of these modules is UNMAINTAINED is not graded — proxy.golang.org 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, not a registry one. Known CVEs in this module graph are D30's question, read from REDACTED and go.sum there.
Dependency pinned to a stale untagged commit: github.com/airyhq/airy · ×4
Resolve the 4 Dependency pinned to a stale untagged commit finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 2 Deprecated module finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (2 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.
3 secret(s) detected. 1 detection(s) were excluded as holding no minted credential in material that runs: a name, reference or comparison rather than a value, a readable phrase or pattern, a value that declares itself fake, or development, test, example, mock or demo material.
REDACTED
What to do
Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 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.
1 of 1084 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 1084 package(s) this repository's committed lockfile installs for a consumer — its 46 production, optional and peer dependency(ies), across 2 product REDACTED manifest(s), and everything those install in turn. Its 56 `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. 6 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. 2 vendored, copied-in or compiled component(s) state no licence this pass can read — missing data, not charged. ★ COVERAGE OF THIS VERDICT: it grades this repository's npm package dependencies and nothing else. The repository also declares a Go module (REDACTED/go.sum), 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.
Banned license: ua-parser-jsdocs/REDACTED:7062
What to do
Resolve the 1 Banned license finding(s) in License Compliance — start with REDACTED. — One of this dimension's main actionable groups (1 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.
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.
9 deducted task-comment markers across 53666 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 9 TodoComment finding(s) in Explicit Debt — start with AiryLoggerFactory.java, REDACTED, create.go. — One of this dimension's main actionable groups (9 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.
1 of 1 documentation facets pass in full. 111 document(s) read across 2 unit(s).
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
3 naming inconsistencies among 56 declarations measured against a convention their peers follow.
`conversationId` spells `Id` where 12 names in the project spell it `ID`REDACTED:137
`getAppExternalURL` spells `URL` where 41 names in the project spell it `Url`frontend/control-center/src/services/getAppExternalURL.ts:6
`checkWithURLValidation` spells `URL` where 41 names in the project spell it `Url`lib/typescript/components/inputs/Input/index.tsx:105
What to do
Resolve the 1 `conversationId` spells `Id` where 12 names in the project spell it `ID` finding(s) in Naming Consistency — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 `getAppExternalURL` spells `URL` where 41 names in the project spell it… finding(s) in Naming Consistency — start with getAppExternalURL.ts. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 `checkWithURLValidation` spells `URL` where 41 names in the project… finding(s) in Naming Consistency — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D22 · Internal API Consistency6.3 / 10Adequate✓ Tool-verified
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.
1 API inconsistencies among 27 exposed members measured against a convention their peers follow.
`k8s.ApplyConfigMap` takes its context.Context last where 2 members of the package take it firstlib/go/k8s/configmaps.go:13
What to do
Resolve the 1 `k8s.ApplyConfigMap` takes its context.Context last where 2 members of… finding(s) in Internal API Consistency — start with configmaps.go. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d22_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.
1 of 11 build units (Go, npm) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesionREDACTED:1
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
11 finding(s): 0 critical, 11 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 9 REDACTED finding(s) in Secrets (history) — start with REDACTED (3), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (9 issue-level).
Resolve the 2 High secret finding(s) in Secrets (history) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
59 finding(s): 0 critical, 13 high, 43 medium, 3 low. 4 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 83 file(s) — `REDACTED`, `REDACTED`, `backend/components/chat-plugin/helm/templates/frontend/ingress.yaml`, `REDACTED`, `backend/components/contacts/helm/templates/deployment.yaml`, … (+78 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 19 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
No action in Static Analysis (SAST) — all 4 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (4 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 55 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (35), REDACTED (20). — One of this dimension's main actionable groups (55 issue-level).
Resolve the 10 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (6), REDACTED (4). — One of this dimension's main actionable groups (10 issue-level).
Resolve the 1 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 260 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (92), REDACTED (78), REDACTED (29). — One of this dimension's main actionable groups (260 warning-level).
Resolve the 67 High IaC finding(s) in IaC & Container Security — start with REDACTED (22), REDACTED (20), REDACTED (10). — One of this dimension's main actionable groups (67 issue-level).
Resolve the 1 Critical IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-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.
260 of 260 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is lib/typescript/translations/translations.ts. Counted over 260 of the 993 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Most significant orphaned file · ×3lib/typescript/translations/translations.ts:1
Dormant codebase
What to do
Resolve the 257 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED (66), Stores.java (17), REDACTED (14). — One of this dimension's main actionable groups (257 recommendation-level).
Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with REDACTED (2), translations.ts. — One of this dimension's main actionable groups (3 recommendation-level).
Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 5 Boundary-crossing change coupling finding(s) in Change Coupling — start with REDACTED (5). — One of this dimension's main actionable groups (5 issue-level).
Resolve the 1 Change coupling finding(s) in Change Coupling — start with Components.ts. — 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 Kubernetes workloads restrict network EGRESS with a NetworkPolicy (or Cilium policy), limiting where a compromised pod can send data or reach a command-and-control server. Presence of committed egress-restricting policy, not runtime enforcement.
Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn — language-agnostic): Kubernetes workloads gate applicability; credits a NetworkPolicy / Cilium policy that restricts egress (policyTypes: [Egress] / egress rules). Reward-leaning (neutral floor climbing to 10, never a deduction — baseline misconfigs stay with D31). Deterministic.
What it measures: Whether Kubernetes workloads confine the kernel boundary — a seccomp profile (RuntimeDefault/Localhost) plus an AppArmor/SELinux mandatory-access-control layer — shrinking the syscall attack surface a container escape would use. Presence of committed confinement config, not runtime enforcement.
Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn): on Kubernetes workloads, credits a seccomp profile (RuntimeDefault/Localhost) and an AppArmor/SELinux MAC layer. Reward-leaning (neutral floor climbing to 10); NotApplicable without workloads. Deterministic.
0/10 workload(s) run every container under a seccomp profile; 0/10 declare an AppArmor/SELinux profile.
No seccomp profile · ×10REDACTED:175
What to do
Resolve the 10 No seccomp profile finding(s) in Kernel & Syscall Confinement — start with REDACTED (2), letsencrypt.yaml (2), REDACTED (2). — One of this dimension's main actionable groups (10 recommendation-level).
Detailed fixes: d41_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the Kubernetes deployment wires runtime threat enforcement — a detection engine (Tetragon/Falco) and/or an admission-control policy gate (Kyverno / OPA Gatekeeper / PodSecurity). Presence of committed policy, not a runtime guarantee.
Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn): on Kubernetes workloads, credits a runtime threat-detection engine (Tetragon TracingPolicy / Falco) and an admission-control policy (Kyverno / OPA Gatekeeper / PodSecurity). Reward-leaning; NotApplicable without workloads. Deterministic.
Resolve the 1 No runtime threat detection finding(s) in Runtime Threat Enforcement. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 No admission-control policy finding(s) in Runtime Threat Enforcement. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d42_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 9 platform declaration(s) and 39 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
✓ On the Gold path — maintain.
Detailed fixes: d44_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives4.8 / 10Weak✓ Tool-verified
Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.
An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. — frontend/chat-plugin/lib/src/airyRenderProps/AiryBubble/index.tsx:35
A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content. (×2) — frontend/inbox/src/pages/Inbox/MessageInput/AudioRecording/WaveformAudio.tsx:65, lib/typescript/components/general/AudioClip/index.tsx:176
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). — lib/typescript/render/components/Video/index.tsx:36
What to do
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
Do you agree with this assessment?
AC2 · Forms & labels5.2 / 10Adequate✓ Tool-verified
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×9) — frontend/chat-plugin/lib/src/airyRenderProps/AiryInputBar/index.tsx:205, frontend/control-center/src/pages/Connectors/Providers/Airy/ChatPlugin/sections/InstallSection/InstallSection.tsx:136, frontend/control-center/src/pages/Connectors/Providers/Airy/ChatPlugin/sections/InstallSection/InstallSection.tsx:156, …
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. (×4) — frontend/chat-plugin/lib/src/airyRenderProps/AiryInputBar/index.tsx:242, frontend/control-center/src/pages/Webhooks/SubscriptionModal/index.tsx:132, frontend/control-center/src/pages/Webhooks/SubscriptionModal/index.tsx:133, …
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). (×18) — frontend/control-center/src/pages/Connectors/ConnectedChannelsList/index.tsx:133, frontend/control-center/src/pages/Connectors/Providers/Facebook/Messenger/FacebookMessengerRequirementsDialog/index.tsx:19, frontend/control-center/src/pages/Connectors/Providers/Google/GoogleBusinessMessagesRequirementsDialog/index.tsx:19, …
This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label. (×6) — frontend/control-center/src/pages/Connectors/Providers/Airy/ChatPlugin/sections/CustomiseSection/ColorSection/ColorPickerSample/index.tsx:12, frontend/control-center/src/pages/Webhooks/WebhooksListItem/index.tsx:131, frontend/inbox/src/components/Dialog/index.tsx:37, …
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. — frontend/control-center/src/pages/Connectors/Providers/Airy/ChatPlugin/sections/CustomiseSection/ColorSection/SampleInput/index.tsx:15
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. — frontend/inbox/src/pages/Tags/index.tsx:163
This <canvas> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label. — lib/typescript/components/general/AudioClip/index.tsx:176
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.
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it. (×5) — frontend/chat-plugin/dev/development.html:2, frontend/control-center/development.html:2, frontend/control-center/index.html:2, …
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — frontend/control-center/public/start.html:2
An iframe with no title (or an empty one) is announced only as "frame". Add a non-empty title describing its content, or an aria-label. — frontend/control-center/src/components/ExternalView/index.tsx:11
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".
A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler. (×39) — frontend/chat-plugin/lib/src/airyRenderProps/AiryBubble/index.tsx:64, frontend/control-center/src/components/Sidebar/index.tsx:87, frontend/control-center/src/components/Sidebar/index.tsx:149, …
This <span> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabIndex={0}, so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabIndex={0}="0" so the element can receive that focus. — frontend/inbox/src/components/ContactDetails/ContactInfoPoint.tsx:124
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.
`.boxButton` sets color: white on background-color: #1578D4 — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — frontend/control-center/public/start.html:78
`.textarea:invalid` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — lib/typescript/components/inputs/TextArea/style.module.scss:26
`.inputInvalid:invalid` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — lib/typescript/components/inputs/TextArea/style.module.scss:37
`.component input:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — lib/typescript/components/inputs/SearchField/style.module.scss:27
`.inputInvalid .input:invalid` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — lib/typescript/components/inputs/Input/style.module.scss:46
`.inputInner:invalid` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — lib/typescript/components/inputs/Input/style.module.scss:145
`.button:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. (×2) — lib/typescript/components/inputs/Dropdown/style.module.scss:42, lib/typescript/components/general/FilterBar/FilterDropdown/index.module.scss:42
`.item:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. (×2) — lib/typescript/components/inputs/Dropdown/style.module.scss:107, lib/typescript/components/general/FilterBar/FilterDropdown/index.module.scss:128
`.buttons button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — lib/typescript/components/general/Pagination/index.module.scss:8
`.buttonScroll:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — lib/typescript/components/general/Carousel/index.module.scss:35
`.audioContainer button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — lib/typescript/components/general/AudioClip/index.module.scss:29
`.closeButton` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — lib/typescript/components/alerts/SettingsModal/ModalHeader.module.scss:22
`.content` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — lib/typescript/components/alerts/SettingsModal/style.module.scss:24
`.errorWrapper button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — lib/typescript/components/alerts/ErrorPopUp/style.module.scss:33
`.actionButton` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — frontend/inbox/src/pages/Tags/TableRow.module.scss:88
`.filterButton` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. (×2) — frontend/inbox/src/pages/Inbox/QuickFilter/Popup.module.scss:77, frontend/inbox/src/pages/Inbox/ConversationListHeader/index.module.scss:105
`.filterButtonSelected` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — frontend/inbox/src/pages/Inbox/QuickFilter/Popup.module.scss:106
`.quickFilterButton` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — frontend/inbox/src/pages/Inbox/QuickFilter/index.module.scss:26
`.filterButton:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — frontend/inbox/src/pages/Inbox/QuickFilter/index.module.scss:63
`.suggestionWrapper` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — frontend/inbox/src/pages/Inbox/Messenger/MessageList/index.module.scss:26
`.displayNameButtons button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. (×3) — frontend/inbox/src/pages/Inbox/Messenger/ConversationMetadata/index.module.scss:74, frontend/inbox/src/pages/Contacts/ContactInformation/index.module.scss:79, frontend/control-center/src/pages/Webhooks/WebhooksListItem/index.module.scss:94
`.recordingIconButton:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — frontend/inbox/src/pages/Inbox/MessageInput/InputOptions.module.scss:123
`.iconButton:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — frontend/inbox/src/pages/Inbox/MessageInput/InputOptions.module.scss:158
`.removeButton` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — frontend/inbox/src/pages/Inbox/MessageInput/InputSelector.module.scss:29
`.messageTextArea` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — frontend/inbox/src/pages/Inbox/MessageInput/index.module.scss:94
`.sendButton` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — frontend/inbox/src/pages/Inbox/MessageInput/index.module.scss:119
`.closedStateButton button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — frontend/inbox/src/pages/Inbox/ConversationListItem/index.module.scss:120
`.openStateButton button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — frontend/inbox/src/pages/Inbox/ConversationListItem/index.module.scss:150
`.searchButton` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — frontend/inbox/src/pages/Inbox/ConversationListHeader/index.module.scss:72
`.container input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — frontend/inbox/src/components/ContactDetails/index.module.scss:67
`button:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — frontend/inbox/src/assets/scss/index.scss:53
`.refreshButton` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. (×4) — frontend/control-center/src/pages/Topics/index.module.scss:103, frontend/control-center/src/pages/Streams/index.module.scss:103, frontend/control-center/src/pages/Status/index.module.scss:93, …
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 — Whether any singleton service captures a scoped/transient dependency — a silent lifetime/threading bug.
Method: Roslyn scan: DI registrations parsed from AddSingleton/Scoped/Transient; each singleton checked for captured shorter-lifetime dependencies. Exhaustive, deterministic.
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 singleton services avoid mutable shared instance state that concurrent callers would race on.
Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.
`LuceneProvider` is a singleton (@Component: the container shares one instance across every request thread) but mutates instance state outside any lock (reader; e.g. `reader` in `refreshReader` at line 92). — backend/components/communication/src/main/java/co/airy/core/communication/lucene/LuceneProvider.java:29
`Api` is a singleton (@Service: the container shares one instance across every request thread) but mutates instance state outside any lock (restTemplate; e.g. `restTemplate` in `onApplicationEvent` at line 175). — backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/api/Api.java:46
`Api` is a singleton (@Service: the container shares one instance across every request thread) but mutates instance state outside any lock (restTemplate; e.g. `restTemplate` in `onApplicationEvent` at line 60). — backend/components/google/connector/src/main/java/co/airy/core/sources/google/services/Api.java:30
`Api` is a singleton (@Component: the container shares one instance across every request thread) but mutates instance state outside any lock (restTemplate; e.g. `restTemplate` in `onApplicationEvent` at line 98). — backend/components/viber/connector/src/main/java/co/airy/core/sources/viber/services/Api.java:34
`Api` is a singleton (@Service: the container shares one instance across every request thread) but mutates instance state outside any lock (restTemplate; e.g. `restTemplate` in `onApplicationEvent` at line 92). — backend/components/whatsapp/connector/src/main/java/co/airy/core/sources/whatsapp/api/Api.java:36
`GitHandler` is a singleton (@Component: the container shares one instance across every request thread) but mutates instance state outside any lock (git; e.g. `git` in `onApplicationEvent` at line 32). — backend/components/installer/src/main/java/co/airy/core/api/components/installer/GitHandler.java:18
`InstallerHandlerCacheManager` is a singleton (@Component: the container shares one instance across every request thread) but mutates instance state outside any lock (resetCache; e.g. `resetCache` in `resetCacheAfterJob` at line 40). — backend/components/installer/src/main/java/co/airy/core/api/components/installer/InstallerHandlerCacheManager.java:22
`Stores` is a singleton (@Component: the container shares one instance across every request thread) but mutates instance state outside any lock (prevoiusCacheMap; e.g. `prevoiusCacheMap` in `storeFromCacheMap` at line 46). — backend/components/installer/src/main/java/co/airy/core/api/components/installer/Stores.java:24
`KafkaStreamsWrapper` is a singleton (@Bean: the container shares one instance across every request thread) but mutates instance state outside any lock (host, port, bufferMemory, bufferedRecordsPerPartition, cacheMaxBytes, cleanup; e.g. `host` in `withAppServerHost` at line 99). — REDACTED:38
`GithubApi` is a singleton (@Component: the container shares one instance across every request thread) but mutates instance state outside any lock (restTemplate; e.g. `restTemplate` in `onApplicationEvent` at line 44). — lib/java/spring/auth/src/main/java/co/airy/spring/auth/oidc/github/GithubApi.java:22
What to do
Java/Kotlin: keep container singletons stateless — move per-request data into locals or a request-scoped bean — or back the state with java.util.concurrent types (ConcurrentHashMap, AtomicInteger/AtomicReference), guard it with synchronized / a Lock (Kotlin: withLock), or mark a flag that is only ever overwritten volatile (@Volatile).
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.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ 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.
Other · Code Health — Unreviewed-generation residue in this repository's JavaScript/TypeScript: functions whose whole body still throws a "not implemented" error, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings and JSX of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's JavaScript/TypeScript: functions that only throw a "not implemented" error, functions that take inputs and return a constant or do nothing, async functions that never await, dead `if (false)` branches, and skeleton classes most of whose methods are holes.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
`startHealthcheck` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — REDACTED:237
`main` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — REDACTED:256
Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition. — frontend/control-center/src/pages/Connectors/Providers/Airy/ChatPlugin/sections/InstallSection/InstallSection.tsx:52
The `if` and its `else` contain the same statements, so no input can make the condition matter. Implement the distinction that was intended, or drop the branch and keep the body. — frontend/inbox/src/services/format/date.ts:16
What to do
Remove the dead code that looks live: delete dead if(false) branches, which read as logic that runs, and either do the real async work or drop the async keyword from fake-async functions, which promise work they never wait for.
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.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
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.
Only 6/8 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `backend/components/schema-registry-manager/src`, `docs/cli-doc`.
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 3 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:3
`REDACTED` schedules updates, but no `package-ecosystem` entry covers `github-actions`, `gomod`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entries to the `updates:` list. — REDACTED:2
What to do
Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
Dependabot is configured but does not watch `github-actions`, `gomod` — add those `package-ecosystem` entries to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
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 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.
`http.Client{` 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. (×9) — REDACTED:40, REDACTED:73, REDACTED:160, …
`fetch(` 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. (×3) — backend/components/schema-registry-manager/src/providers/karapace.ts:98, backend/components/schema-registry-manager/src/providers/karapace.ts:105, backend/components/schema-registry-manager/src/providers/karapace.ts:112
`http.Get(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — REDACTED:63
What to do
Give every `http.Client` an explicit `Timeout` (never call `http.Get`/`http.Post` or `http.DefaultClient`, which have none), or build each request with `http.NewRequestWithContext` under a `context.WithTimeout`; add retry with back-off (`hashicorp/go-retryablehttp`) and a breaker (`sony/gobreaker`) around dependencies that fail.
Bound every outbound call: pass `signal: AbortSignal.timeout(ms)` to `fetch`, set `timeout` on the axios instance (`axios.create({ timeout })`), and add retries with back-off (`axios-retry`, `p-retry`) and a breaker (`opossum`, `cockatiel`) around dependencies that fail.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
Do you agree with this assessment?
R1 · Type Safety10.0 / 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.
35 duplicated blocks under frontend/control-center/src/pages/ have copies in at least two of the sibling directories Apps, Catalog, Connectors, Inbox, LLMConsumers, LLMs (+5 more sibling(s) not listed) — 27 of them are reported below, and 8 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 35 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 35 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 35 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. — frontend/control-center/src/pages/Apps/index.tsx:14
33 duplicated blocks under frontend/ have copies in at least two of the sibling directories chat-plugin, control-center, inbox — 20 of them are reported below, and 13 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 33 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 33 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 33 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. — frontend/control-center/src/components/TopBar/index.tsx:1
13 duplicated blocks under lib/typescript/render/providers/ have copies in at least two of the sibling directories chatplugin, google, meta, twilio, viber — 10 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 13 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 13 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 13 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. — lib/typescript/render/providers/chatplugin/components/RichCard/index.tsx:27
11 duplicated blocks under frontend/control-center/src/pages/Connectors/Providers/ have copies in at least two of the sibling directories Airy, Facebook, Google, Instagram, Twilio, Viber (+1 more sibling(s) not listed) — 9 of them are reported below, and 2 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 11 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 11 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 11 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. — frontend/control-center/src/pages/Connectors/Providers/Google/GoogleConnect.tsx:17
10 duplicated blocks under the repository root have copies in at least two of the sibling directories backend, frontend, lib — 7 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 10 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 10 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 10 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — frontend/chat-plugin/lib/src/config.ts:7
frontend/control-center/src/components/TopBar/index.tsx:1 · frontend/inbox/src/components/TopBar/index.tsx:1 — these 2 files are line-for-line copies of one another — 212 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. — frontend/control-center/src/components/TopBar/index.tsx:1
frontend/control-center/src/pages/Schemas/SchemaItem/SchemaDescription/EnrichedSchemaSection/index.tsx:140 · frontend/control-center/src/pages/Schemas/SchemaItem/SchemaDescription/SchemaSection/index.tsx:109 — the two spans are one implementation copied and then locally edited — 535 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. — frontend/control-center/src/pages/Schemas/SchemaItem/SchemaDescription/EnrichedSchemaSection/index.tsx:140
frontend/control-center/src/pages/Connectors/Providers/Google/GoogleConnect.tsx:17 · frontend/control-center/src/pages/Connectors/Providers/Viber/ViberConnect.tsx:13 — the two spans are one implementation copied and then locally edited — 576 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. — frontend/control-center/src/pages/Connectors/Providers/Google/GoogleConnect.tsx:17
frontend/inbox/src/reducers/data/conversations/index.ts:65 · frontend/inbox/src/reducers/data/conversationsFilter/index.ts:39 — the two spans are one implementation copied and then locally edited — 467 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. — frontend/inbox/src/reducers/data/conversations/index.ts:65
frontend/control-center/src/pages/Apps/index.tsx:14 · frontend/control-center/src/pages/Connectors/index.tsx:14 — 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. — frontend/control-center/src/pages/Apps/index.tsx:14
frontend/inbox/src/pages/Contacts/ContactInformation/index.tsx:91 · frontend/inbox/src/pages/Inbox/Messenger/ConversationMetadata/index.tsx:162 — the two spans are one implementation copied and then locally edited — 424 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. — frontend/inbox/src/pages/Contacts/ContactInformation/index.tsx:91
frontend/control-center/src/pages/Streams/ListMode/ListMode.tsx:35 · frontend/control-center/src/pages/Topics/ListMode/ListMode.tsx:30 — the two spans are one implementation copied and then locally edited — 435 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. — frontend/control-center/src/pages/Streams/ListMode/ListMode.tsx:35
frontend/control-center/src/pages/Connectors/ConnectedChannelsList/ChannelsListItem/index.tsx:17 · frontend/control-center/src/pages/Inbox/ChannelsList/ChannelListItem/index.tsx:16 — the two spans are one implementation copied and then locally edited — 404 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. — frontend/control-center/src/pages/Connectors/ConnectedChannelsList/ChannelsListItem/index.tsx:17
frontend/control-center/src/pages/Connectors/Providers/Viber/ViberConnect.tsx:13 · frontend/control-center/src/pages/Connectors/Providers/WhatsappBusinessCloud/WhatsappConnect.tsx:13 — the two spans are one implementation copied and then locally edited — 425 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. — frontend/control-center/src/pages/Connectors/Providers/Viber/ViberConnect.tsx:13
frontend/control-center/src/actions/channel/index.ts:28 · frontend/inbox/src/actions/channel/index.ts:31 — the two spans are one implementation copied and then locally edited — 578 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. — frontend/control-center/src/actions/channel/index.ts:28
lib/typescript/components/cta/Button/index.tsx:22 · lib/typescript/components/cta/SmartButton/index.tsx:26 — 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. — lib/typescript/components/cta/Button/index.tsx:22
frontend/control-center/src/reducers/data/channels/index.ts:7 · frontend/inbox/src/reducers/data/channels/index.ts:7 — 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. — frontend/control-center/src/reducers/data/channels/index.ts:7
lib/typescript/render/providers/chatplugin/components/RichCard/index.tsx:27 · lib/typescript/render/providers/google/components/RichCard/index.tsx:18 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — lib/typescript/render/providers/chatplugin/components/RichCard/index.tsx:27
frontend/control-center/src/pages/Connectors/Providers/Facebook/Messenger/FacebookConnect.tsx:13 · frontend/control-center/src/pages/Connectors/Providers/WhatsappBusinessCloud/WhatsappConnect.tsx:13 — 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. — frontend/control-center/src/pages/Connectors/Providers/Facebook/Messenger/FacebookConnect.tsx:13
frontend/control-center/src/pages/Schemas/SchemaItem/SchemaInfo.tsx:37 · frontend/control-center/src/pages/Streams/StreamItem/StreamInfo.tsx:24 — the two spans are one implementation copied and then locally edited — 323 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. — frontend/control-center/src/pages/Schemas/SchemaItem/SchemaInfo.tsx:37
lib/typescript/components/general/FilterBar/FilterDropdown/index.tsx:36 · lib/typescript/components/inputs/Dropdown/index.tsx:29 — 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. — lib/typescript/components/general/FilterBar/FilterDropdown/index.tsx:36
lib/typescript/render/providers/meta/MetaRender.tsx:244 · lib/typescript/render/providers/meta/MetaRender.tsx:455 — 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/typescript/render/providers/meta/MetaRender.tsx:244
frontend/control-center/src/pages/Schemas/JoinMode/PhaseOne.tsx:79 · frontend/control-center/src/pages/Schemas/JoinMode/PhaseOne.tsx:144 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — frontend/control-center/src/pages/Schemas/JoinMode/PhaseOne.tsx:79
lib/typescript/render/providers/chatplugin/ChatPluginRender.tsx:77 · lib/typescript/render/providers/meta/MetaRender.tsx:340 — 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. — lib/typescript/render/providers/chatplugin/ChatPluginRender.tsx:77
frontend/chat-plugin/lib/src/airyRenderProps/AiryInputBar/InputSelector/index.tsx:20 · frontend/inbox/src/pages/Inbox/MessageInput/InputSelector.tsx:24 — the two spans are one implementation copied and then locally edited — 241 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. — frontend/chat-plugin/lib/src/airyRenderProps/AiryInputBar/InputSelector/index.tsx:20
lib/typescript/render/providers/chatplugin/chatPluginModel.ts:59 · lib/typescript/render/providers/google/googleModel.ts:28 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — lib/typescript/render/providers/chatplugin/chatPluginModel.ts:59
frontend/control-center/src/pages/Connectors/ConnectedChannelsList/DisableModal/index.tsx:36 · frontend/control-center/src/pages/Webhooks/UnsubscribeModal/index.tsx:37 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — frontend/control-center/src/pages/Connectors/ConnectedChannelsList/DisableModal/index.tsx:36
frontend/control-center/src/pages/Connectors/Providers/Google/GoogleBusinessMessagesRequirementsDialog/index.tsx:13 · frontend/control-center/src/pages/Connectors/Providers/Instagram/InstagramRequirementsDialog/index.tsx:13 — 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. — frontend/control-center/src/pages/Connectors/Providers/Google/GoogleBusinessMessagesRequirementsDialog/index.tsx:13
frontend/control-center/src/pages/Schemas/SchemaItem/SchemaDescription/EnrichedSchemaSection/index.tsx:71 · frontend/control-center/src/pages/Schemas/SchemaItem/SchemaDescription/SchemaSection/index.tsx:64 — the two spans are one implementation copied and then locally edited — 225 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. — frontend/control-center/src/pages/Schemas/SchemaItem/SchemaDescription/EnrichedSchemaSection/index.tsx:71
frontend/chat-plugin/lib/src/config.ts:7 · lib/typescript/model/ChatpluginConfig.ts:25 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — frontend/chat-plugin/lib/src/config.ts:7
frontend/control-center/src/pages/Streams/Creation/index.tsx:363 · frontend/control-center/src/pages/Streams/Creation/index.tsx:407 — 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. — frontend/control-center/src/pages/Streams/Creation/index.tsx:363
lib/typescript/render/providers/meta/MetaRender.tsx:301 · lib/typescript/render/providers/meta/MetaRender.tsx:515 — 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/typescript/render/providers/meta/MetaRender.tsx:301
frontend/control-center/src/pages/Connectors/ConnectedChannelsList/index.tsx:124 · frontend/control-center/src/pages/Inbox/ChannelsList/index.tsx:120 — the two spans are one implementation copied and then locally edited — 193 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. — frontend/control-center/src/pages/Connectors/ConnectedChannelsList/index.tsx:124
REDACTED:147 · REDACTED:178 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — REDACTED:147
frontend/control-center/src/pages/Connectors/Providers/Facebook/Messenger/FacebookMessengerRequirementsDialog/index.tsx:16 · frontend/control-center/src/pages/Connectors/Providers/Instagram/InstagramRequirementsDialog/index.tsx:17 — 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. — frontend/control-center/src/pages/Connectors/Providers/Facebook/Messenger/FacebookMessengerRequirementsDialog/index.tsx:16
frontend/control-center/src/pages/Connectors/Providers/Facebook/Messenger/FacebookConnect.tsx:141 · frontend/control-center/src/pages/Connectors/Providers/Google/GoogleConnect.tsx:135 · frontend/control-center/src/pages/Connectors/Providers/WhatsappBusinessCloud/WhatsappConnect.tsx:137 — the 3 copies are spread across 3 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. — frontend/control-center/src/pages/Connectors/Providers/Facebook/Messenger/FacebookConnect.tsx:141
frontend/control-center/src/pages/Schemas/ListMode/ListMode.tsx:52 · frontend/control-center/src/pages/Status/index.tsx:51 — 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. — frontend/control-center/src/pages/Schemas/ListMode/ListMode.tsx:52
frontend/inbox/src/components/Dialog/index.tsx:17 · frontend/inbox/src/components/DialogCustomizable/index.tsx:23 — 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. — frontend/inbox/src/components/Dialog/index.tsx:17
frontend/chat-plugin/lib/src/components/dragAndDrop/index.tsx:11 · frontend/inbox/src/pages/Inbox/Messenger/MessengerContainer/index.tsx:115 — the two spans are one implementation copied and then locally edited — 183 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. — frontend/chat-plugin/lib/src/components/dragAndDrop/index.tsx:11
frontend/control-center/src/pages/Connectors/Providers/Airy/ChatPlugin/sections/ConnectNewChatPlugin.tsx:51 · frontend/control-center/src/pages/Connectors/Providers/Airy/ChatPlugin/sections/CreateUpdateSection/CreateUpdateSection.tsx:57 — 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. — frontend/control-center/src/pages/Connectors/Providers/Airy/ChatPlugin/sections/ConnectNewChatPlugin.tsx:51
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.
frontend/control-center/src/actions/streams/index.ts:5 imports react-markdown/lib/ast-to-react, 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. — frontend/control-center/src/actions/streams/index.ts:5
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.
metaOutbound has cyclomatic complexity 50 and cognitive complexity 64; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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/typescript/render/providers/meta/MetaRender.tsx:342
Sidebar has cyclomatic complexity 42 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — frontend/control-center/src/components/Sidebar/index.tsx:41
CustomiseSection has cyclomatic complexity 41 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — frontend/control-center/src/pages/Connectors/Providers/Airy/ChatPlugin/sections/CustomiseSection/CustomiseSection.tsx:23
InputOptions has cyclomatic complexity 39 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. — frontend/inbox/src/pages/Inbox/MessageInput/InputOptions.tsx:41
lastMessageIsIcon has cyclomatic complexity 33 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. — lib/typescript/render/SourceMessagePreview.tsx:158
metaInbound has cyclomatic complexity 32 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. — lib/typescript/render/providers/meta/MetaRender.tsx:220
render has cyclomatic complexity 32 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — lib/typescript/render/providers/meta/MetaRender.tsx:37
ColorSection has cyclomatic complexity 31 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 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. — frontend/control-center/src/pages/Connectors/Providers/Airy/ChatPlugin/sections/CustomiseSection/ColorSection/index.tsx:36
lastMessageIsText has cyclomatic complexity 30 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. — lib/typescript/render/SourceMessagePreview.tsx:48
(anonymous) has cyclomatic complexity 27 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/typescript/render/providers/twilio/TwilioRender.tsx:50
ConnectorConfig has cyclomatic complexity 27 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. — frontend/control-center/src/pages/Connectors/ConnectorConfig/index.tsx:38
InputToggleSection has cyclomatic complexity 25 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. — REDACTED:40
mapContent has cyclomatic complexity 24 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. — lib/typescript/render/providers/chatplugin/ChatPluginRender.tsx:79
MessageInput has cyclomatic complexity 24 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. — frontend/inbox/src/pages/Inbox/MessageInput/index.tsx:58
ItemInfo has cyclomatic complexity 24 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. — frontend/control-center/src/pages/Status/ComponentListItem/ItemInfo.tsx:31
sendMessage has cyclomatic complexity 23 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — frontend/inbox/src/pages/Inbox/MessageInput/index.tsx:234
googleInbound has cyclomatic complexity 22 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. — lib/typescript/render/providers/google/GoogleRender.tsx:60
(anonymous) has cyclomatic complexity 21 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — frontend/control-center/src/pages/Connectors/ConfigureConnector/SetConfigInputs/SetConfigInputs.tsx:25
getTemplateConfig has cyclomatic complexity 19 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. — frontend/control-center/src/pages/Connectors/Providers/Airy/ChatPlugin/sections/InstallSection/InstallSection.tsx:49
TopBar has cyclomatic complexity 18 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — frontend/control-center/src/components/TopBar/index.tsx:37
(anonymous) has cyclomatic complexity 18 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — lib/typescript/render/providers/meta/MetaRender.tsx:143
ContactDetails has cyclomatic complexity 18 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — frontend/inbox/src/components/ContactDetails/index.tsx:44
allReducer has cyclomatic complexity 18 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — frontend/inbox/src/reducers/data/conversations/index.ts:184
(anonymous) has cyclomatic complexity 17 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — frontend/inbox/src/selectors/conversations.ts:81
SideColumnContent has cyclomatic complexity 17 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. — frontend/control-center/src/pages/Catalog/CatalogItemDetails/index.tsx:184
TopBar has cyclomatic complexity 17 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. — frontend/inbox/src/components/TopBar/index.tsx:38
FacebookConnect has cyclomatic complexity 17 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — frontend/control-center/src/pages/Connectors/Providers/Facebook/Messenger/FacebookConnect.tsx:23
WhatsappConnect has cyclomatic complexity 17 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — frontend/control-center/src/pages/Connectors/Providers/WhatsappBusinessCloud/WhatsappConnect.tsx:23
GoogleConnect has cyclomatic complexity 16 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — frontend/control-center/src/pages/Connectors/Providers/Google/GoogleConnect.tsx:27
googleOutbound has cyclomatic complexity 15 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — lib/typescript/render/providers/google/GoogleRender.tsx:152
ConnectorWrapper has cyclomatic complexity 15 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — frontend/control-center/src/pages/Connectors/ConnectorWrapper/index.tsx:38
Tooltip has cyclomatic complexity 15 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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/typescript/components/tooltip/index.tsx:20
Creation has cyclomatic complexity 15 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — frontend/control-center/src/pages/Streams/Creation/index.tsx:31
ChatPluginConnect has cyclomatic complexity 14 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — frontend/control-center/src/pages/Connectors/Providers/Airy/ChatPlugin/ChatPluginConnect.tsx:46
SubscriptionModal has cyclomatic complexity 14 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — frontend/control-center/src/pages/Webhooks/SubscriptionModal/index.tsx:24
(anonymous) has cyclomatic complexity 14 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — frontend/inbox/src/components/IconChannel/index.tsx:93
TwilioConnect has cyclomatic complexity 14 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — frontend/control-center/src/pages/Connectors/Providers/Twilio/TwilioConnect.tsx:28
ViberConnect has cyclomatic complexity 14 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — frontend/control-center/src/pages/Connectors/Providers/Viber/ViberConnect.tsx:23
WhatsAppInteractive has cyclomatic complexity 14 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — lib/typescript/render/providers/meta/components/WhatsAppInteractive/index.tsx:16
Chat has cyclomatic complexity 13 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — frontend/chat-plugin/lib/src/components/chat/index.tsx:56
Do you agree with this assessment?
R3 · Large Files9.5 / 10Exemplary✓ 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.
frontend/inbox/src/pages/Inbox/MessageInput/index.tsx has 516 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/inbox/src/pages/Inbox/MessageInput/index.tsx:1
frontend/control-center/src/pages/Streams/Creation/index.tsx has 501 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/control-center/src/pages/Streams/Creation/index.tsx:1
lib/typescript/render/providers/meta/MetaRender.tsx has 473 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — lib/typescript/render/providers/meta/MetaRender.tsx:1
lib/typescript/components/inputs/Input/index.tsx has 452 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/typescript/components/inputs/Input/index.tsx:1
frontend/control-center/src/pages/Connectors/Providers/Airy/ChatPlugin/sections/CustomiseSection/ColorSection/index.tsx has 438 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/control-center/src/pages/Connectors/Providers/Airy/ChatPlugin/sections/CustomiseSection/ColorSection/index.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 Coverage0.1 / 10Critical✓ Tool-verified
React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.
Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.
No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×40) — lib/typescript/translations/translations.ts:1, frontend/inbox/src/pages/Inbox/MessageInput/index.tsx:1, lib/typescript/render/providers/meta/MetaRender.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 · Tooling6.7 / 10Adequate✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each REDACTED script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: REDACTED scanned for test/lint/typecheck script wiring. Deterministic presence check.
test ✓ · lint ✓ · typecheck ✗ — read from this repository's REDACTED scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
Add `tsc --noEmit` as REDACTED scripts and run them in CI.
Do you agree with this assessment?
R7 · Dead Code1.4 / 10Critical✓ 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.
3 file(s) (~388 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — backend/components/schema-registry-manager/src
Unreachable from the 8 application, 4 tooling and 13 test entry point(s) detected in this repo. This repository declares no build, type-check or test script, so nothing here would fail on a wrong deletion — confirm by hand that nothing loads each file (including by a path built at runtime) before removing it. An undetected custom entry would make these reachable.
no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (lib/typescript/translations/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — lib/typescript/translations/translations.ts
no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (lib/typescript/render/renderProviders.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 (×4) — lib/typescript/render/providers/meta/MetaRender.tsx, lib/typescript/render/providers/chatplugin/ChatPluginRender.tsx, lib/typescript/render/providers/google/GoogleRender.tsx, …
no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (lib/typescript/httpclient/src/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — lib/typescript/httpclient/src/client.ts
no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (frontend/chat-plugin/lib/src/AiryChatPlugin.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 — frontend/chat-plugin/lib/src/components/chat/index.tsx
no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 11 in-repo import(s) from 11 other file(s) do name it (lib/typescript/render/components/Image/index.tsx, lib/typescript/render/providers/meta/MetaRender.tsx, lib/typescript/render/providers/meta/components/ButtonTemplate/index.tsx and 8 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — lib/typescript/render/providers/meta/MetaModel.ts
no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (frontend/chat-plugin/lib/src/components/chat/index.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 (×4) — frontend/chat-plugin/lib/src/airyRenderProps/AiryInputBar/index.tsx, frontend/chat-plugin/lib/src/websocket/index.ts, frontend/chat-plugin/lib/src/airyRenderProps/AiryBubble/index.tsx, …
no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (lib/typescript/render/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — lib/typescript/render/SourceMessagePreview.tsx
no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (lib/typescript/components/general/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×4) — lib/typescript/components/general/AudioClip/index.tsx, lib/typescript/components/general/Carousel/index.tsx, lib/typescript/components/general/FilterBar/index.tsx, …
no import path from any entry point (8 application, 4 tooling, 13 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 (×2) — frontend/control-center/src/pages/Inbox/ChannelsList/index.tsx, frontend/control-center/src/pages/Catalog/CatalogSearchBar/CatalogSearchBar.tsx
no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 4 in-repo import(s) from 4 other file(s) do name it (lib/typescript/render/providers/chatplugin/ChatPluginRender.tsx, lib/typescript/render/providers/chatplugin/components/RichCard/Media/index.tsx, lib/typescript/render/providers/chatplugin/components/RichCard/index.tsx and 1 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — lib/typescript/render/providers/chatplugin/chatPluginModel.ts
no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (lib/typescript/components/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — lib/typescript/components/tooltip/index.tsx
no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 5 in-repo import(s) from 5 other file(s) do name it (lib/typescript/render/providers/google/GoogleRender.tsx, lib/typescript/render/providers/google/components/RichCard/Media/index.tsx, lib/typescript/render/providers/google/components/RichCard/index.tsx and 2 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — lib/typescript/render/providers/google/googleModel.ts
no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (frontend/chat-plugin/lib/src/airyRenderProps/AiryInputBar/index.tsx, frontend/chat-plugin/lib/src/components/chat/index.tsx, frontend/chat-plugin/lib/src/websocket/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — frontend/chat-plugin/lib/src/api/index.tsx
no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (lib/typescript/render/services/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — lib/typescript/render/services/mediaAttachments.ts
no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (lib/typescript/components/general/FilterBar/index.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 — lib/typescript/components/general/FilterBar/FilterDropdown/index.tsx
no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (lib/typescript/components/general/AudioClip/services/index.ts, lib/typescript/components/general/AudioClip/services/progressBar.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 — lib/typescript/components/general/AudioClip/services/drawCanvasPaths.ts
no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (frontend/control-center/src/pages/Inbox/ChannelsList/index.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 — frontend/control-center/src/pages/Inbox/ChannelsList/ChannelListItem/index.tsx
no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (frontend/chat-plugin/lib/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — frontend/chat-plugin/lib/src/AiryChatPlugin.tsx
no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (lib/typescript/components/cta/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — lib/typescript/components/cta/SmartButton/index.tsx, lib/typescript/components/cta/Button/index.tsx
no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (lib/typescript/render/providers/google/GoogleRender.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 — lib/typescript/render/providers/google/components/Suggestions/index.tsx
no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (lib/typescript/websocketclient/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — lib/typescript/websocketclient/payload.ts
no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (lib/typescript/components/alerts/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — lib/typescript/components/alerts/NotificationComponent/index.tsx
no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (lib/typescript/model/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — lib/typescript/model/ChatpluginConfig.ts
no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (lib/typescript/render/providers/meta/components/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — lib/typescript/render/providers/meta/components/WhatsAppTemplate/index.tsx, lib/typescript/render/providers/meta/components/WhatsAppInteractive/index.tsx
no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (frontend/chat-plugin/lib/src/airyRenderProps/AiryInputBar/index.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 — frontend/chat-plugin/lib/src/airyRenderProps/AiryInputBar/InputSelector/index.tsx
no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (lib/typescript/components/inputs/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — lib/typescript/components/inputs/Dropdown/index.tsx
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 REDACTED — installs work only by hoisting accident. (×12) — frontend/control-center/src/components/ChannelAvatar/index.tsx:2, frontend/control-center/src/pages/Connectors/Providers/Airy/ChatPlugin/sections/CustomiseSection/CustomiseSection.tsx:4, integration/chat-plugin/end_conversation.spec.ts:1, …
Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×10) — REDACTED:55, REDACTED:56, REDACTED:12, …
Declared in backend/components/schema-registry-manager/src/REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. — backend/components/schema-registry-manager/src/REDACTED:8
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
Do you agree with this assessment?
R9 · Circular Imports4.3 / 10Weak✓ Tool-verified
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
frontend/control-center/src/pages/Schemas/JoinMode/PhaseOne.tsx → frontend/control-center/src/pages/Schemas/index.tsx → frontend/control-center/src/pages/Schemas/JoinMode/index.tsx → frontend/control-center/src/pages/Schemas/JoinMode/PhaseOne.tsx (one verified cycle inside a mutually-dependent group of 5 files) — frontend/control-center/src/pages/Schemas/JoinMode/PhaseOne.tsx:6
Other · Security — Only what this repository's own non-C# files could be read for was assessed — and because this repository commits the configuration that serves its own HTTP surface, that configuration could be read in full for the security response headers it sets. Nothing else in this dimension was assessed: the transport, cookie, input-validation and crypto controls are read from a source model that was not loaded for this repository’s language, so their absence here is not a finding about this repository.
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `nginx.conf` is committed to this repository and declares the server that serves it, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — frontend/inbox/nginx.conf:32
What to do
Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
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 functions that make a cancellable request accept or pass on a context.Context or 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 1/18 functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial) accept a context.Context or an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, a cancelled request, a shutdown, an expired deadline. Take a `signal` (Go: `ctx context.Context`) 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.
`doFetchFromBackend` 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/typescript/httpclient/src/client.ts:134
`doFetchFromBackendForKafkaTopics` 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/typescript/httpclient/src/client.ts:158
`post` calls `http.NewRequest(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`. — lib/go/httpclient/httpclient.go:28
`getComponentsDetailsFromCloud` calls `http.Get(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`. — REDACTED:61
`getData` 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 })`. (×2) — frontend/control-center/src/actions/streams/index.ts:174, backend/components/schema-registry-manager/src/providers/karapace.ts:97
`deleteData` 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 })`. (×2) — frontend/control-center/src/actions/streams/index.ts:181, backend/components/schema-registry-manager/src/providers/karapace.ts:104
`postData` 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 })`. (×2) — frontend/control-center/src/actions/streams/index.ts:188, backend/components/schema-registry-manager/src/providers/karapace.ts:111
`getResumeToken` 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 })`. — frontend/chat-plugin/lib/src/api/index.tsx:60
`authenticate` 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 })`. — frontend/chat-plugin/lib/src/api/index.tsx:73
`sendFlinkSQL` calls `http.NewRequest(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`. — REDACTED:18
`sendMessage` calls `http.NewRequest(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`. — REDACTED:137
`sendFlinkSQLConfluent` calls `http.NewRequest(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`. — REDACTED:185
`getFlinkResult` calls `http.NewRequest(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`. — REDACTED:235
`getFlinkResultConfluent` calls `http.NewRequest(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`. — REDACTED:329
What to do
Thread a context.Context or an AbortSignal through functions that make requests, so the work stops when its caller gives up.
Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `NullPointerException` (Java, Kotlin, Scala), `ArgumentError.notNull` (Dart) or `ArgumentNullException` (F#'s `nullArg`) tells the caller a parameter was null when it provably was not.
Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements (or a repository exception type deriving from it) controlled by an `if` — directly or through the `using`, `lock` or `try` that wraps the throw — whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`); in the `else` branch, for a conjunct of the admitting condition that is FALSE of a non-null `p`. Range guards are read for bounds that leave nothing and for a `p > C.Count` bound whose index then reaches `C[p]`, `C.RemoveAt(p)` or a method of the same type that indexes with it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
`catch` 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. — lib/typescript/httpclient/src/client.ts:189
`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. (×3) — lib/java/spring/web/src/main/java/co/airy/spring/web/filters/HttpPostLogFilter.java:92, lib/java/spring/web/src/main/java/co/airy/spring/web/filters/RequestLoggingFilter.java:113, lib/java/spring/auth/src/main/java/co/airy/spring/auth/token/AuthenticationFilter.java: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. (×2) — lib/java/spring/web/src/main/java/co/airy/spring/web/filters/RequestLoggingFilter.java:76, backend/model/metadata/src/main/java/co/airy/model/metadata/MetadataObjectMapper.java:81
`if err != nil` 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. (×7) — REDACTED:112, REDACTED:104, cli/pkg/helm/helm.go:242, …
`resp, _ := json.Marshal(response)` writes the call's error to `_` and then uses `resp` as if the call succeeded. When `json.Marshal` fails, `resp` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `resp` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. — infrastructure/controller/pkg/endpoints/cluster_update.go:60
`if deleteErr != nil` handles a failure of `deleteErr` but reports `err`, which the earlier `if err != nil { return … }` already proved nil here: the real failure is lost and a nil error is reported (or returned as success) in its place. Report `deleteErr`. — infrastructure/controller/pkg/endpoints/components_delete.go:49
`resp, _ := json.Marshal(responseComponents)` writes the call's error to `_` and then uses `resp` as if the call succeeded. When `json.Marshal` fails, `resp` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `resp` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. (×2) — infrastructure/controller/pkg/endpoints/components_delete.go:60, infrastructure/controller/pkg/endpoints/components_update.go:68
`resp, _ := json.Marshal(&ServicesResponse{Services: componentsMap})` writes the call's error to `_` and then uses `resp` as if the call succeeded. When `json.Marshal` fails, `resp` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `resp` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. — infrastructure/controller/pkg/endpoints/services.go:41
`h.cleanupJob()` returns an error, and the statement drops it: when `h.cleanupJob` fails nothing records it and the code after it runs as if it had succeeded. Check it (`if err := h.cleanupJob(); err != nil { … }`) and return or log it with what was being done, or assign it to `_` with a comment saying why the failure cannot matter. — cli/pkg/helm/helm.go:104
`body, _ := ioutil.ReadAll(resp.Body)` writes the call's error to `_` and then uses `body` as if the call succeeded. When `ioutil.ReadAll` fails, `body` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `body` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. — cli/pkg/cmd/root.go:63
`response, _ := json.Marshal(payloads.StreamsCreateResponsePayload{ Name: expr.Name, OutputTopic: expr.Name, })` writes the call's error to `_` and then uses `response` as if the call succeeded. When `json.Marshal` fails, `response` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `response` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. — backend/components/streams/streams_create.go:104
`response, _ := json.Marshal(payloads.StreamsDeleteResponsePayload{ Name: expr.Name, })` writes the call's error to `_` and then uses `response` as if the call succeeded. When `json.Marshal` fails, `response` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `response` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. — backend/components/streams/streams_delete.go:65
`response, _ := json.Marshal(res)` writes the call's error to `_` and then uses `response` as if the call succeeded. When `json.Marshal` fails, `response` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `response` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. — backend/components/streams/streams_info.go:46
What to do
Swallowed exception (caught, then discarded)
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 `REDACTED` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
`info` at line 36 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — lib/java/spring/async/src/main/java/co/airy/spring/async/AsyncExecutorConfig.java:36
`info` at line 300 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — REDACTED:300
`info` at line 301 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — REDACTED:301
`error` at line 75 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. (×2) — lib/java/kafka/core/src/main/java/co/airy/kafka/core/KafkaConsumerWrapper.java:75, backend/components/google/connector/src/main/java/co/airy/core/sources/google/Connector.java:75
`error` at line 259 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — backend/model/contact/src/main/java/co/airy/model/contact/Contact.java:259
`error` at line 302 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — backend/model/contact/src/main/java/co/airy/model/contact/Contact.java:302
`warn` at line 100 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — backend/components/whatsapp/events-router/src/main/java/co/airy/core/sources/whatsapp/EventsRouter.java:100
`warn` at line 113 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — backend/components/whatsapp/events-router/src/main/java/co/airy/core/sources/whatsapp/EventsRouter.java:113
`error` at line 67 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. (×2) — backend/components/whatsapp/connector/src/main/java/co/airy/core/sources/whatsapp/Connector.java:67, backend/components/installer/src/main/java/co/airy/core/api/components/installer/InstallerController.java:67
`error` at line 80 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — backend/components/whatsapp/connector/src/main/java/co/airy/core/sources/whatsapp/Connector.java:80
`error` at line 62 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — backend/components/viber/connector/src/main/java/co/airy/core/sources/viber/Connector.java:62
`warn` at line 83 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — backend/components/twilio/events-router/src/main/java/co/airy/core/sources/twilio/EventsRouter.java:83
`error` at line 64 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. (×2) — backend/components/twilio/connector/src/main/java/co/airy/core/sources/twilio/Connector.java:64, backend/components/ibm-watson-assistant/src/main/java/co/airy/core/ibm_watson_assistant_connector/MessageHandler.java:64
`error` at line 76 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — backend/components/twilio/connector/src/main/java/co/airy/core/sources/twilio/Connector.java:76
`info` at line 45 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — backend/components/rasa/src/main/java/co/airy/core/rasa_connector/RasaConnectorService.java:45
`error` at line 49 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. (×2) — backend/components/rasa/src/main/java/co/airy/core/rasa_connector/RasaConnectorService.java:49, backend/components/cognigy/src/main/java/co/airy/core/cognigy_connector/CognigyConnectorService.java:49
`error` at line 63 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. (×2) — backend/components/rasa/src/main/java/co/airy/core/rasa_connector/RasaConnectorService.java:63, backend/components/cognigy/src/main/java/co/airy/core/cognigy_connector/CognigyConnectorService.java:63
`error` at line 169 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — backend/components/installer/src/main/java/co/airy/core/api/components/installer/HelmJobHandler.java:169
`error` at line 40 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — backend/components/installer/src/main/java/co/airy/core/api/components/installer/InstallerController.java:40
`error` at line 54 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. (×2) — backend/components/installer/src/main/java/co/airy/core/api/components/installer/InstallerController.java:54, backend/components/ibm-watson-assistant/src/main/java/co/airy/core/ibm_watson_assistant_connector/IbmWatsonAssistantConnectorService.java:54
`info` at line 59 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — backend/components/installer/src/main/java/co/airy/core/api/components/installer/InstallerHandler.java:59
`info` at line 80 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — backend/components/installer/src/main/java/co/airy/core/api/components/installer/InstallerHandler.java:80
`error` at line 94 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. (×2) — backend/components/installer/src/main/java/co/airy/core/api/components/installer/InstallerHandlerCacheManager.java:94, backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/Connector.java:94
`error` at line 69 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — backend/components/ibm-watson-assistant/src/main/java/co/airy/core/ibm_watson_assistant_connector/IbmWatsonAssistantConnectorService.java:69
`error` at line 66 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — backend/components/google/connector/src/main/java/co/airy/core/sources/google/Connector.java:66
`error` at line 27 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — backend/components/google/connector/src/main/java/co/airy/core/sources/google/GoogleConfig.java:27
`warn` at line 112 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — backend/components/facebook/events-router/src/main/java/co/airy/core/sources/facebook/EventsRouter.java:112
`error` at line 128 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — backend/components/facebook/events-router/src/main/java/co/airy/core/sources/facebook/EventsRouter.java:128
`warn` at line 131 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — backend/components/facebook/events-router/src/main/java/co/airy/core/sources/facebook/EventsRouter.java:131
`error` at line 81 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. (×2) — backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/Connector.java:81, backend/components/chat-plugin/src/main/java/co/airy/core/chat_plugin/config/Jwt.java:81
`error` at line 107 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — backend/components/communication/src/main/java/co/airy/core/communication/AsyncSendMessagesHandler.java:107
`error` at line 103 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — backend/components/chat-plugin/src/main/java/co/airy/core/chat_plugin/config/Jwt.java:103
Other · Code Health — Whether strict null checking is enabled and not undermined by heavy `!` assertion — TypeScript's `strictNullChecks` (which `strict` turns on) is what makes `string` exclude `null` and `undefined`, and the postfix `!` is the operator that silences it.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
1/3 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
What to do
The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
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 — 5 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.
D36 Supply-chain Provenance & Signing — 5 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X10 Duplicated predicate — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 5 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
Not included — 41 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.
AX4 Dependency direction — not applicable to a transaction-script/CRUD architecture (the inward-dependency rule is for layered/clean styles)
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
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 — The runtime tier booted this repository's service, but crawled PUBLIC routes only — add a Playwright storageState (e.g. playwright/.auth/user.json) or a test auth-setup to crawl authenticated screens rendered 0/1 surface(s) × 2 renders render failed for http://127.0.0.1:32768: page.addStyleTag: Refused to apply inline style because it violates the following Content Security Policy directive: "default-src 'none'". Either the 'unsafe-in ran the repo's cypress suite against the booted app but captured no surfaces (suite failed to install/run, or visited no pages) — see runtime diagnostics. This repository also has a user interface (247 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates) that the booted service does not serve, and this scan has no strategy that reaches it — so no WCAG success criterion was verified in a rendered page on this run. That is a gap in OUR tooling, not a finding about your application: nothing here says the interface is inaccessible. The static accessibility checks still ran.
AXS1 Runtime exposed surface — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
D11 Test Reliability — Test reliability not scored — polyglot repository, one half has no runner
D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Aggregate roots were found in only one source directory (model), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D25 ADR Conformance — no ADRs to check
D27 Navigability — D27 reads resolved call sites in the languages it reads only — this repository's production source is .go, .py, .ts, .tsx, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D32 Data Compliance (PII/GDPR) — 2 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not measured — polyglot repository, one half has no runner
DM1 Domain Modelling — applicable but not scored (2 signals for this style, 2 needed — the count is met but a required primary signal is absent): 1 aggregate root(s) (types guarding their own state behind command methods — this language has no AggregateRoot base to inherit); 17 value object(s)
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
M4 Documentation accuracy — Not applicable: the 114 current-state document(s) make no claim of a kind M4 checks. 110 claim(s) of kinds M4 does not check were not checked (path 10, command argument 12, install 6, environment variable 11, route 70, cd 1); M4 checks only links and versions and artefact counts.
P8 Schema migrations — sql-migrate is declared, but this repository defines no table or model of its own, so there is no database schema here for this check to judge
P9 Domain vs controller coverage — coverage data present for 4 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, 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 yarn lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — X26 reached only 41% of this repository's production lines — typescript (31,363 lines), javascript (510 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X27 Collection changed while being enumerated — X27 reached only 41% of this repository's production lines — typescript (31,363 lines), javascript (510 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.
AC4 · Keyboard semantics· Click handler on a non-interactive <div> · ×26
Click handler on a non-interactive <div> frontend/chat-plugin/lib/src/airyRenderProps/AiryBubble/index.tsx:64— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> frontend/control-center/src/components/Sidebar/index.tsx:87— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> frontend/control-center/src/components/Sidebar/index.tsx:149— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> frontend/control-center/src/components/TopBar/index.tsx:124— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> frontend/control-center/src/components/TopBar/index.tsx:163— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> frontend/control-center/src/components/TopBar/index.tsx:177— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> frontend/control-center/src/components/TopBar/index.tsx:185— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> frontend/control-center/src/components/TopBar/index.tsx:193— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> frontend/control-center/src/components/TopBar/index.tsx:201— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> frontend/control-center/src/components/TopBar/index.tsx:216— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> frontend/control-center/src/pages/Connectors/ChannelCard/index.tsx:45— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> frontend/control-center/src/pages/Connectors/Providers/Airy/ChatPlugin/sections/CustomiseSection/ColorSection/ColorPicker/index.tsx:14— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> frontend/control-center/src/pages/Connectors/Providers/Airy/ChatPlugin/sections/CustomiseSection/ColorSection/ColorPickerSample/index.tsx:12— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> frontend/control-center/src/pages/Schemas/SchemaItem/SchemaInfo.tsx:78— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> frontend/control-center/src/pages/Schemas/index.tsx:39— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> frontend/control-center/src/pages/Schemas/index.tsx:50— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> frontend/control-center/src/pages/Streams/Creation/index.tsx:187— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> frontend/control-center/src/pages/Streams/Creation/index.tsx:217— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> frontend/control-center/src/pages/Streams/Creation/index.tsx:375— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> frontend/control-center/src/pages/Streams/Creation/index.tsx:419— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> frontend/control-center/src/pages/Streams/StreamItem/StreamInfo.tsx:56— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> frontend/control-center/src/pages/Topics/TopicItem/TopicDescription/TopicDescription.tsx:96— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> frontend/control-center/src/pages/Topics/TopicItem/TopicInfo.tsx:28— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> frontend/control-center/src/pages/Webhooks/WebhooksListItem/index.tsx:131— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> frontend/inbox/src/components/ContactDetails/Expandable.tsx:19— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
+ 1 more in this group — see findings.md.
AC2 · Forms & labels· <button> with no accessible text · ×18
<button> with no accessible text frontend/control-center/src/pages/Connectors/ConnectedChannelsList/index.tsx:133— 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 frontend/control-center/src/pages/Connectors/Providers/Facebook/Messenger/FacebookMessengerRequirementsDialog/index.tsx:19— 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 frontend/control-center/src/pages/Connectors/Providers/Google/GoogleBusinessMessagesRequirementsDialog/index.tsx:19— 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 frontend/control-center/src/pages/Connectors/Providers/Instagram/InstagramRequirementsDialog/index.tsx:20— 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 frontend/control-center/src/pages/Connectors/Providers/Twilio/TwilioRequirementsDialog/index.tsx:19— 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 frontend/control-center/src/pages/Inbox/ChannelsList/index.tsx:129— 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 frontend/control-center/src/pages/Schemas/ListMode/ListMode.tsx:105— 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 frontend/control-center/src/pages/Status/index.tsx:81— 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 frontend/control-center/src/pages/Streams/ListMode/ListMode.tsx:89— 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 frontend/control-center/src/pages/Topics/ListMode/ListMode.tsx:74— 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 frontend/inbox/src/pages/Contacts/ContactInformation/index.tsx:165— 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 frontend/inbox/src/pages/Contacts/ContactInformation/index.tsx:168— 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 frontend/inbox/src/pages/Inbox/ConversationListHeader/index.tsx:84— 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 frontend/inbox/src/pages/Inbox/ConversationListItem/index.tsx:46— 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 frontend/inbox/src/pages/Inbox/Messenger/ConversationMetadata/index.tsx:299— 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 frontend/inbox/src/pages/Inbox/Messenger/ConversationMetadata/index.tsx:302— 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 lib/typescript/components/alerts/ErrorPopUp/index.tsx:16— 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 lib/typescript/components/general/FilterBar/FilterDropdown/index.tsx:93— 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 · ×9
<input> without a programmatic label frontend/chat-plugin/lib/src/airyRenderProps/AiryInputBar/index.tsx:205— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label frontend/control-center/src/pages/Schemas/JoinMode/PhaseOne.tsx:87— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label frontend/control-center/src/pages/Schemas/JoinMode/PhaseOne.tsx:152— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label frontend/control-center/src/pages/Schemas/SchemaItem/SchemaInfo.tsx:59— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label frontend/control-center/src/pages/Webhooks/SubscriptionModal/index.tsx:132— 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 frontend/control-center/src/pages/Webhooks/SubscriptionModal/index.tsx:133— 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 frontend/control-center/src/pages/Webhooks/SubscriptionModal/index.tsx:187— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label frontend/control-center/src/pages/Webhooks/SubscriptionModal/index.tsx:191— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label frontend/inbox/src/pages/Tags/TableRow.tsx:109— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC4 · Keyboard semantics· Click handler on a non-interactive <span> · ×8
Click handler on a non-interactive <span> frontend/control-center/src/pages/Connectors/ConnectorConfig/index.tsx:149— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <span> frontend/control-center/src/pages/Connectors/ConnectorConfig/index.tsx:161— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <span> frontend/control-center/src/pages/Connectors/Providers/Airy/ChatPlugin/ChatPluginConnect.tsx:175— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <span> frontend/control-center/src/pages/Connectors/Providers/Airy/ChatPlugin/ChatPluginConnect.tsx:182— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <span> frontend/control-center/src/pages/Connectors/Providers/Airy/ChatPlugin/ChatPluginConnect.tsx:190— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <span> frontend/control-center/src/pages/LLMConsumers/EmptyState/index.tsx:23— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <span> frontend/control-center/src/pages/LLMs/EmptyState/index.tsx:23— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <span> frontend/control-center/src/pages/Webhooks/EmptyState/index.tsx:23— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
AC2 · Forms & labels· Custom control with no accessible name on <div> · ×6
Custom control with no accessible name on <div> frontend/control-center/src/pages/Connectors/Providers/Airy/ChatPlugin/sections/CustomiseSection/ColorSection/ColorPickerSample/index.tsx:12— This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
Custom control with no accessible name on <div> frontend/control-center/src/pages/Webhooks/WebhooksListItem/index.tsx:131— This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
Custom control with no accessible name on <div> frontend/inbox/src/components/Dialog/index.tsx:37— This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
Custom control with no accessible name on <div> frontend/inbox/src/components/DialogCustomizable/index.tsx:43— This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
Custom control with no accessible name on <div> frontend/inbox/src/pages/Contacts/ContactListItem/index.tsx:127— This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
Custom control with no accessible name on <div> lib/typescript/components/alerts/NotificationComponent/index.tsx:82— This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
Boundary-crossing change coupling: REDACTED ↔ translations.ts frontend/control-center/src/pages/Catalog/CatalogItemDetails/index.tsx:1— `frontend/control-center/src/pages/Catalog/CatalogItemDetails/index.tsx` (context control-center) and `lib/typescript/translations/translations.ts` (context typescript) sit in DIFFERENT parts of the tree yet change together 73% of the time (8 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `b38e5b2e` [#3841] Add translations catalog components (#3972); `e1307bdc` [#3667] Added IBM and Amazon S3 to catalog (#3707); `6e687ae3` [#3485] Add notify me catalog (#3705) — run `git show` on any of them.
Boundary-crossing change coupling: REDACTED ↔ translations.ts frontend/control-center/src/pages/Connectors/index.tsx:1— `frontend/control-center/src/pages/Connectors/index.tsx` (context control-center) and `lib/typescript/translations/translations.ts` (context typescript) sit in DIFFERENT parts of the tree yet change together 65% of the time (13 of the 20 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 13 shared commits counted here, the most recent 3 are `31da2df1` [#4034] Add filter in catalog (#4041); `ae1e34c4` [#3927] Added airy contacts to catalog (#3932); `be728f9c` [#3730] cypress connector update (#3731) — run `git show` on any of them.
Boundary-crossing change coupling: REDACTED ↔ translations.ts frontend/control-center/src/pages/Connectors/ConnectorConfig/index.tsx:1— `frontend/control-center/src/pages/Connectors/ConnectorConfig/index.tsx` (context control-center) and `lib/typescript/translations/translations.ts` (context typescript) sit in DIFFERENT parts of the tree yet change together 65% of the time (13 of the 20 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 13 shared commits counted here, the most recent 3 are `69da5506` [#3642] Added tooltips channel connectors (#3859); `8c921637` [#3822] Added Notification Configurations (#3834); `4a1da54c` [#3800] Minor fixes (#3803) — run `git show` on any of them.
Boundary-crossing change coupling: REDACTED ↔ Components.ts frontend/control-center/src/pages/Connectors/ConnectorConfig/index.tsx:1— `frontend/control-center/src/pages/Connectors/ConnectorConfig/index.tsx` (context control-center) and `lib/typescript/model/Components.ts` (context typescript) sit in DIFFERENT parts of the tree yet change together 64% of the time (7 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `954ca329` [#3648] Added getMergedConnectors as useSelector (#3780); `ef9c6992` [#3669] remove component naming types in the control center (#3676); `5e79bade` [#3662] Update DynamoDB with configuration values and remove enum Com… — run `git show` on any of them.
Boundary-crossing change coupling: REDACTED ↔ translations.ts frontend/control-center/src/pages/Catalog/CatalogCard/index.tsx:1— `frontend/control-center/src/pages/Catalog/CatalogCard/index.tsx` (context control-center) and `lib/typescript/translations/translations.ts` (context typescript) sit in DIFFERENT parts of the tree yet change together 56% of the time (9 of the 16 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `31da2df1` [#4034] Add filter in catalog (#4041); `0c799df4` [#3935] Enhance catalog filter (#3983); `4a1da54c` [#3800] Minor fixes (#3803) — run `git show` on any of them.
AC2 · Forms & labels· <textarea> without a programmatic label · ×4
<textarea> without a programmatic label frontend/chat-plugin/lib/src/airyRenderProps/AiryInputBar/index.tsx:242— 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.
<textarea> without a programmatic label frontend/control-center/src/pages/Connectors/Providers/Airy/ChatPlugin/sections/InstallSection/InstallSection.tsx:136— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<textarea> without a programmatic label frontend/control-center/src/pages/Connectors/Providers/Airy/ChatPlugin/sections/InstallSection/InstallSection.tsx:156— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<textarea> without a programmatic label frontend/inbox/src/pages/Inbox/MessageInput/index.tsx:503— 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 <p> · ×4
Click handler on a non-interactive <p> frontend/control-center/src/pages/Schemas/SchemaItem/SchemaInfo.tsx:74— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <p> frontend/control-center/src/pages/Streams/StreamItem/StreamInfo.tsx:46— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <p> frontend/control-center/src/pages/Streams/StreamItem/StreamInfo.tsx:52— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <p> frontend/control-center/src/pages/Topics/TopicItem/TopicInfo.tsx:24— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
AC1 · Text alternatives· <img> without a text alternative · ×1
<img> without a text alternative frontend/chat-plugin/lib/src/airyRenderProps/AiryBubble/index.tsx:35— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
AC2 · Forms & labels· Custom control with no accessible name on <canvas> · ×1
Custom control with no accessible name on <canvas> lib/typescript/components/general/AudioClip/index.tsx:176— This <canvas> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
AC3 · Page structure· <iframe> without a title · ×1
<iframe> without a title frontend/control-center/src/components/ExternalView/index.tsx:11— 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· Click handler on a non-interactive <section> · ×1
Click handler on a non-interactive <section> frontend/control-center/src/pages/Status/ComponentListItem/index.tsx:38— 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· Hover-only interaction on <span> · ×1
Hover-only interaction on <span> frontend/inbox/src/components/ContactDetails/ContactInfoPoint.tsx:124— This <span> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabIndex={0}, so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabIndex={0}="0" so the element can receive that focus.
Banned license: ua-parser-js docs/REDACTED:7062— `ua-parser-js` 0.7.35 is published on registry.npmjs.org under `AGPL-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.
Unlisted import 'assets' frontend/control-center/src/components/ChannelAvatar/index.tsx:2— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'chat-plugin' frontend/control-center/src/pages/Connectors/Providers/Airy/ChatPlugin/sections/CustomiseSection/CustomiseSection.tsx:4— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'chat-plugin-handles' integration/chat-plugin/end_conversation.spec.ts:1— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'components' frontend/control-center/src/components/TopBar/index.tsx:3— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'dates' frontend/inbox/src/pages/Inbox/Messenger/MessageList/index.tsx:10— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'handles' frontend/control-center/src/pages/Connectors/ChannelCard/index.tsx:9— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'httpclient' frontend/control-center/src/actions/catalog/index.ts:4— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'model' frontend/control-center/src/actions/catalog/index.ts:5— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'react-router' frontend/control-center/src/components/Sidebar/index.tsx:3— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'render' frontend/inbox/src/pages/Inbox/ConversationListItem/index.tsx:6— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'websocketclient' frontend/control-center/src/components/AiryWebsocket/index.tsx:3— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
No assertions: canListChannels backend/components/admin/src/test/java/co/airy/core/admin/ChannelsControllerTest.java:82— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: canUpdateChannel backend/components/admin/src/test/java/co/airy/core/admin/ChannelsControllerTest.java:103— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: canManageTags backend/components/admin/src/test/java/co/airy/core/admin/TagsControllerTest.java:61— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: canListTemplates backend/components/admin/src/test/java/co/airy/core/admin/TemplatesControllerTest.java:102— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: canListUsers backend/components/admin/src/test/java/co/airy/core/admin/UsersControllerTest.java:102— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: canListWebhooks backend/components/admin/src/test/java/co/airy/core/admin/WebhooksControllerTest.java:148— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: canManageWebhook backend/components/admin/src/test/java/co/airy/core/admin/WebhooksControllerTest.java:81— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: canGetResumeTokenAsUser backend/components/chat-plugin/src/test/java/co/airy/core/chat_plugin/ChatControllerTest.java:184— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: canResumeConversation backend/components/chat-plugin/src/test/java/co/airy/core/chat_plugin/ChatControllerTest.java:140— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: canFetchConversationsInfo backend/components/communication/src/test/java/co/airy/core/communication/ConversationsInfoTest.java:67— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: canFetchAllConversations backend/components/communication/src/test/java/co/airy/core/communication/ConversationsListTest.java:111— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: canFetchPaginated backend/components/communication/src/test/java/co/airy/core/communication/ConversationsListTest.java:126— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: canFilterByCombinedQueries backend/components/communication/src/test/java/co/airy/core/communication/ConversationsListTest.java:213— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: canFilterByConversationId backend/components/communication/src/test/java/co/airy/core/communication/ConversationsListTest.java:169— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: canFilterByDisplayName backend/components/communication/src/test/java/co/airy/core/communication/ConversationsListTest.java:179— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: canFilterByDisplayNameIgnoringCasing backend/components/communication/src/test/java/co/airy/core/communication/ConversationsListTest.java:185— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: canFilterByMetadata backend/components/communication/src/test/java/co/airy/core/communication/ConversationsListTest.java:229— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: canFilterByTagIds backend/components/communication/src/test/java/co/airy/core/communication/ConversationsListTest.java:191— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: canFilterByUnreadMessageCount backend/components/communication/src/test/java/co/airy/core/communication/ConversationsListTest.java:203— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: canFilterByUnreadMessageCountRange backend/components/communication/src/test/java/co/airy/core/communication/ConversationsListTest.java:198— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: canFilterForUnknownNames backend/components/communication/src/test/java/co/airy/core/communication/ConversationsListTest.java:224— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: canFindBySource backend/components/communication/src/test/java/co/airy/core/communication/ConversationsListTest.java:208— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: canHandleAnEmptyPayload backend/components/communication/src/test/java/co/airy/core/communication/ConversationsTagTest.java:109— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: canTagAndUntagConversations backend/components/communication/src/test/java/co/airy/core/communication/ConversationsTagTest.java:63— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: canSetAndRemoveStateFromConversations backend/components/communication/src/test/java/co/airy/core/communication/ConversationsUpdateTest.java:72— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
FunctionTooLong: index.Creation frontend/control-center/src/pages/Streams/Creation/index.tsx:31— FunctionTooLong — Creation runs 408 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 308 over it, 4.08× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: index.MessageInput frontend/inbox/src/pages/Inbox/MessageInput/index.tsx:58— FunctionTooLong — MessageInput runs 393 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 293 over it, 3.93× 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: index.ColorSection frontend/control-center/src/pages/Connectors/Providers/Airy/ChatPlugin/sections/CustomiseSection/ColorSection/index.tsx:36— FunctionTooLong — ColorSection runs 355 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 255 over it, 3.55× 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: CustomiseSection.CustomiseSection frontend/control-center/src/pages/Connectors/Providers/Airy/ChatPlugin/sections/CustomiseSection/CustomiseSection.tsx:23— FunctionTooLong — CustomiseSection runs 277 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 177 over it, 2.77× 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: index.CatalogItemDetails frontend/control-center/src/pages/Catalog/CatalogItemDetails/index.tsx:37— FunctionTooLong — CatalogItemDetails runs 262 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 162 over it, 2.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.
FunctionTooLong: index.ConversationMetadata frontend/inbox/src/pages/Inbox/Messenger/ConversationMetadata/index.tsx:55— FunctionTooLong — ConversationMetadata runs 242 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 142 over it, 2.42× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: index.InputToggleSection REDACTED:40— FunctionTooLong — InputToggleSection runs 229 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 129 over it, 2.29× 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: index.Chat frontend/chat-plugin/lib/src/components/chat/index.tsx:56— FunctionTooLong — Chat runs 221 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 121 over it, 2.21× 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: index.CatalogCard frontend/control-center/src/pages/Catalog/CatalogCard/index.tsx:49— FunctionTooLong — CatalogCard runs 221 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 121 over it, 2.21× 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: index.TopBar frontend/control-center/src/components/TopBar/index.tsx:37— FunctionTooLong — TopBar runs 202 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 102 over it, 2.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.
FunctionTooLong: index.TopBar frontend/inbox/src/components/TopBar/index.tsx:38— FunctionTooLong — TopBar runs 200 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 100 over it, 2.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: Popup.PopUpFilter frontend/inbox/src/pages/Inbox/QuickFilter/Popup.tsx:46— FunctionTooLong — PopUpFilter 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.
FunctionTooLong: index.Catalog frontend/control-center/src/pages/Catalog/index.tsx:30— FunctionTooLong — Catalog runs 184 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 84 over it, 1.84× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: index.AiryInputBar frontend/chat-plugin/lib/src/airyRenderProps/AiryInputBar/index.tsx:26— FunctionTooLong — AiryInputBar runs 181 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 81 over it, 1.81× 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: InputOptions.InputOptions frontend/inbox/src/pages/Inbox/MessageInput/InputOptions.tsx:41— FunctionTooLong — InputOptions runs 174 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 74 over it, 1.74× 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: index.ConnectorWrapper frontend/control-center/src/pages/Connectors/ConnectorWrapper/index.tsx:38— FunctionTooLong — ConnectorWrapper runs 173 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 73 over it, 1.73× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: index.ContactDetails frontend/inbox/src/components/ContactDetails/index.tsx:44— FunctionTooLong — ContactDetails runs 170 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 70 over it, 1.70× 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: index.SchemaSection frontend/control-center/src/pages/Schemas/SchemaItem/SchemaDescription/SchemaSection/index.tsx:33— FunctionTooLong — SchemaSection 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.
FunctionTooLong: index.SubscriptionModal frontend/control-center/src/pages/Webhooks/SubscriptionModal/index.tsx:24— FunctionTooLong — SubscriptionModal runs 166 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 66 over it, 1.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.
FunctionTooLong: index.LLMConsumers frontend/control-center/src/pages/LLMConsumers/index.tsx:34— FunctionTooLong — LLMConsumers runs 154 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 54 over it, 1.54× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: ChatPluginConnect.ChatPluginConnect frontend/control-center/src/pages/Connectors/Providers/Airy/ChatPlugin/ChatPluginConnect.tsx:46— FunctionTooLong — ChatPluginConnect runs 150 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 50 over it, 1.50× 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: index.Tags frontend/inbox/src/pages/Tags/index.tsx:51— FunctionTooLong — Tags runs 146 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 46 over it, 1.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: InstallSection.InstallSection frontend/control-center/src/pages/Connectors/Providers/Airy/ChatPlugin/sections/InstallSection/InstallSection.tsx:13— FunctionTooLong — InstallSection runs 143 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 43 over it, 1.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: PhaseOne.PhaseOne frontend/control-center/src/pages/Schemas/JoinMode/PhaseOne.tsx:21— FunctionTooLong — PhaseOne runs 141 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 41 over it, 1.41× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: PhaseTwo.PhaseTwo frontend/control-center/src/pages/Schemas/JoinMode/PhaseTwo.tsx:25— FunctionTooLong — PhaseTwo runs 139 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 39 over it, 1.39× 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.
+ 22 more in this group — see findings.md.
D30 · Dependency Vulnerabilities· Medium CVE · ×41
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 16 more in this group — see findings.md.
R4 · Test Coverage· No test reaches this file · ×40
No test reaches this file lib/typescript/translations/translations.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file frontend/inbox/src/pages/Inbox/MessageInput/index.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 lib/typescript/render/providers/meta/MetaRender.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 frontend/control-center/src/pages/Streams/Creation/index.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 frontend/control-center/src/pages/Connectors/Providers/Airy/ChatPlugin/sections/CustomiseSection/ColorSection/index.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 lib/typescript/httpclient/src/client.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file frontend/control-center/src/pages/Catalog/CatalogItemDetails/index.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 frontend/inbox/src/pages/Inbox/Messenger/ConversationMetadata/index.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 frontend/chat-plugin/lib/src/components/chat/index.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 frontend/control-center/src/pages/Catalog/CatalogCard/index.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 frontend/inbox/src/reducers/data/conversations/index.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file frontend/control-center/src/pages/Connectors/Providers/Airy/ChatPlugin/sections/CustomiseSection/CustomiseSection.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 lib/typescript/render/providers/meta/MetaModel.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file frontend/control-center/src/pages/Schemas/SchemaItem/SchemaDescription/EnrichedSchemaSection/index.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 frontend/inbox/src/pages/Inbox/QuickFilter/Popup.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 REDACTED: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 frontend/chat-plugin/lib/src/airyRenderProps/AiryInputBar/index.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 frontend/control-center/src/components/TopBar/index.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 frontend/control-center/src/pages/Catalog/index.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 frontend/inbox/src/components/TopBar/index.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 frontend/control-center/src/pages/Connectors/ConnectorWrapper/index.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 REDACTED: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 frontend/inbox/src/components/ContactDetails/index.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 frontend/inbox/src/pages/Inbox/MessageInput/InputOptions.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 lib/typescript/render/SourceMessagePreview.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.
+ 15 more in this group — see findings.md.
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×39
Focus outline removed in CSS without a :focus replacement lib/typescript/components/inputs/TextArea/style.module.scss:26— `.textarea:invalid` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement lib/typescript/components/inputs/TextArea/style.module.scss:37— `.inputInvalid:invalid` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement lib/typescript/components/inputs/SearchField/style.module.scss:27— `.component input:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement lib/typescript/components/inputs/Input/style.module.scss:46— `.inputInvalid .input:invalid` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement lib/typescript/components/inputs/Input/style.module.scss:145— `.inputInner:invalid` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement lib/typescript/components/inputs/Dropdown/style.module.scss:42— `.button:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement lib/typescript/components/inputs/Dropdown/style.module.scss:107— `.item:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement lib/typescript/components/general/Pagination/index.module.scss:8— `.buttons button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement lib/typescript/components/general/FilterBar/FilterDropdown/index.module.scss:42— `.button:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement lib/typescript/components/general/FilterBar/FilterDropdown/index.module.scss:128— `.item:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement lib/typescript/components/general/Carousel/index.module.scss:35— `.buttonScroll:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement lib/typescript/components/general/AudioClip/index.module.scss:29— `.audioContainer button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement lib/typescript/components/alerts/SettingsModal/ModalHeader.module.scss:22— `.closeButton` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement lib/typescript/components/alerts/SettingsModal/style.module.scss:24— `.content` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement lib/typescript/components/alerts/ErrorPopUp/style.module.scss:33— `.errorWrapper button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement frontend/inbox/src/pages/Tags/TableRow.module.scss:88— `.actionButton` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement frontend/inbox/src/pages/Inbox/QuickFilter/Popup.module.scss:77— `.filterButton` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement frontend/inbox/src/pages/Inbox/QuickFilter/Popup.module.scss:106— `.filterButtonSelected` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement frontend/inbox/src/pages/Inbox/QuickFilter/index.module.scss:26— `.quickFilterButton` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement frontend/inbox/src/pages/Inbox/QuickFilter/index.module.scss:63— `.filterButton:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement frontend/inbox/src/pages/Inbox/Messenger/MessageList/index.module.scss:26— `.suggestionWrapper` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement frontend/inbox/src/pages/Inbox/Messenger/ConversationMetadata/index.module.scss:74— `.displayNameButtons button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement frontend/inbox/src/pages/Inbox/MessageInput/InputOptions.module.scss:123— `.recordingIconButton:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement frontend/inbox/src/pages/Inbox/MessageInput/InputOptions.module.scss:158— `.iconButton:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement frontend/inbox/src/pages/Inbox/MessageInput/InputSelector.module.scss:29— `.removeButton` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Outbound HTTP without resilience REDACTED:40— `http.Client{` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience REDACTED:73— `http.Client{` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience REDACTED:160— `http.Client{` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience REDACTED:214— `http.Client{` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience REDACTED:251— `http.Client{` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience REDACTED:275— `http.Client{` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience REDACTED:337— `http.Client{` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience REDACTED:369— `http.Client{` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience REDACTED:398— `http.Client{` 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 backend/components/schema-registry-manager/src/providers/karapace.ts:98— `fetch(` 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 backend/components/schema-registry-manager/src/providers/karapace.ts:105— `fetch(` 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 backend/components/schema-registry-manager/src/providers/karapace.ts:112— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience REDACTED:63— `http.Get(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Swallowed exception (caught, then discarded) lib/typescript/httpclient/src/client.ts:189— `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) lib/java/spring/web/src/main/java/co/airy/spring/web/filters/HttpPostLogFilter.java: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/java/spring/web/src/main/java/co/airy/spring/web/filters/RequestLoggingFilter.java:113— `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/java/spring/auth/src/main/java/co/airy/spring/auth/token/AuthenticationFilter.java:59— `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) REDACTED:112— `if err != nil` 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) REDACTED:104— `if err != nil` 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) cli/pkg/helm/helm.go:242— `if err != nil` 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) cli/pkg/helm/helm.go:249— `if err != nil` 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) cli/pkg/cmd/root.go:60— `if err != nil` 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) cli/pkg/cmd/root.go:87— `if err != nil` 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) REDACTED:104— `if err != nil` 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.
Stateful singleton: LuceneProvider backend/components/communication/src/main/java/co/airy/core/communication/lucene/LuceneProvider.java:29— `LuceneProvider` is a singleton (@Component: the container shares one instance across every request thread) but mutates instance state outside any lock (reader; e.g. `reader` in `refreshReader` at line 92).
Stateful singleton: Api backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/api/Api.java:46— `Api` is a singleton (@Service: the container shares one instance across every request thread) but mutates instance state outside any lock (restTemplate; e.g. `restTemplate` in `onApplicationEvent` at line 175).
Stateful singleton: Api backend/components/google/connector/src/main/java/co/airy/core/sources/google/services/Api.java:30— `Api` is a singleton (@Service: the container shares one instance across every request thread) but mutates instance state outside any lock (restTemplate; e.g. `restTemplate` in `onApplicationEvent` at line 60).
Stateful singleton: Api backend/components/viber/connector/src/main/java/co/airy/core/sources/viber/services/Api.java:34— `Api` is a singleton (@Component: the container shares one instance across every request thread) but mutates instance state outside any lock (restTemplate; e.g. `restTemplate` in `onApplicationEvent` at line 98).
Stateful singleton: Api backend/components/whatsapp/connector/src/main/java/co/airy/core/sources/whatsapp/api/Api.java:36— `Api` is a singleton (@Service: the container shares one instance across every request thread) but mutates instance state outside any lock (restTemplate; e.g. `restTemplate` in `onApplicationEvent` at line 92).
Stateful singleton: GitHandler backend/components/installer/src/main/java/co/airy/core/api/components/installer/GitHandler.java:18— `GitHandler` is a singleton (@Component: the container shares one instance across every request thread) but mutates instance state outside any lock (git; e.g. `git` in `onApplicationEvent` at line 32).
Stateful singleton: InstallerHandlerCacheManager backend/components/installer/src/main/java/co/airy/core/api/components/installer/InstallerHandlerCacheManager.java:22— `InstallerHandlerCacheManager` is a singleton (@Component: the container shares one instance across every request thread) but mutates instance state outside any lock (resetCache; e.g. `resetCache` in `resetCacheAfterJob` at line 40).
Stateful singleton: Stores backend/components/installer/src/main/java/co/airy/core/api/components/installer/Stores.java:24— `Stores` is a singleton (@Component: the container shares one instance across every request thread) but mutates instance state outside any lock (prevoiusCacheMap; e.g. `prevoiusCacheMap` in `storeFromCacheMap` at line 46).
Stateful singleton: KafkaStreamsWrapper REDACTED:38— `KafkaStreamsWrapper` is a singleton (@Bean: the container shares one instance across every request thread) but mutates instance state outside any lock (host, port, bufferMemory, bufferedRecordsPerPartition, cacheMaxBytes, cleanup; e.g. `host` in `withAppServerHost` at line 99).
Stateful singleton: GithubApi lib/java/spring/auth/src/main/java/co/airy/spring/auth/oidc/github/GithubApi.java:22— `GithubApi` is a singleton (@Component: the container shares one instance across every request thread) but mutates instance state outside any lock (restTemplate; e.g. `restTemplate` in `onApplicationEvent` at line 44).
X2 · Cancellation propagation· Async function without AbortSignal · ×10
Async function without AbortSignal: doFetchFromBackend lib/typescript/httpclient/src/client.ts:134— `doFetchFromBackend` 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: doFetchFromBackendForKafkaTopics lib/typescript/httpclient/src/client.ts:158— `doFetchFromBackendForKafkaTopics` 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: getData frontend/control-center/src/actions/streams/index.ts:174— `getData` 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: deleteData frontend/control-center/src/actions/streams/index.ts:181— `deleteData` 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: postData frontend/control-center/src/actions/streams/index.ts:188— `postData` 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: getResumeToken frontend/chat-plugin/lib/src/api/index.tsx:60— `getResumeToken` 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: authenticate frontend/chat-plugin/lib/src/api/index.tsx:73— `authenticate` 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: getData backend/components/schema-registry-manager/src/providers/karapace.ts:97— `getData` 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: deleteData backend/components/schema-registry-manager/src/providers/karapace.ts:104— `deleteData` 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: postData backend/components/schema-registry-manager/src/providers/karapace.ts:111— `postData` 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 })`.
TodoComment lib/java/log/src/main/java/co/airy/log/AiryLoggerFactory.java:22— // TODO production logging — 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 REDACTED:38— // TODO This is slow compared to the DataTypeConverter implementation — 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 infrastructure/controller/pkg/configmap-controller/create.go:51— //TODO extract from annotation — 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 infrastructure/controller/pkg/configmap-controller/update.go:29— //TODO: Hanlde variable number of replicas — 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 backend/model/event/src/main/java/co/airy/model/event/payload/ChannelUpdated.java:24— // TODO record channel update date — 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 backend/model/event/src/main/java/co/airy/model/event/payload/TagEvent.java:25— // TODO record channel update date — 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 backend/components/whatsapp/events-router/src/main/java/co/airy/core/sources/whatsapp/MessageMapper.java:33— // TODO implement remaining fields — 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 backend/components/webhook/consumer/src/main/java/co/airy/core/webhook/consumer/Sender.java:55— // 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 backend/components/installer/src/main/java/co/airy/core/api/components/installer/CatalogHandler.java:42— //TODO: throws exception instead — 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.
X3 · Exception handling· Discarded error (assigned to `_`, then its result used) · ×8
Discarded error (assigned to `_`, then its result used) infrastructure/controller/pkg/endpoints/cluster_update.go:60— `resp, _ := json.Marshal(response)` writes the call's error to `_` and then uses `resp` as if the call succeeded. When `json.Marshal` fails, `resp` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `resp` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line.
Discarded error (assigned to `_`, then its result used) infrastructure/controller/pkg/endpoints/components_delete.go:60— `resp, _ := json.Marshal(responseComponents)` writes the call's error to `_` and then uses `resp` as if the call succeeded. When `json.Marshal` fails, `resp` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `resp` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line.
Discarded error (assigned to `_`, then its result used) infrastructure/controller/pkg/endpoints/components_update.go:68— `resp, _ := json.Marshal(responseComponents)` writes the call's error to `_` and then uses `resp` as if the call succeeded. When `json.Marshal` fails, `resp` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `resp` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line.
Discarded error (assigned to `_`, then its result used) infrastructure/controller/pkg/endpoints/services.go:41— `resp, _ := json.Marshal(&ServicesResponse{Services: componentsMap})` writes the call's error to `_` and then uses `resp` as if the call succeeded. When `json.Marshal` fails, `resp` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `resp` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line.
Discarded error (assigned to `_`, then its result used) cli/pkg/cmd/root.go:63— `body, _ := ioutil.ReadAll(resp.Body)` writes the call's error to `_` and then uses `body` as if the call succeeded. When `ioutil.ReadAll` fails, `body` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `body` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line.
Discarded error (assigned to `_`, then its result used) backend/components/streams/streams_create.go:104— `response, _ := json.Marshal(payloads.StreamsCreateResponsePayload{ Name: expr.Name, OutputTopic: expr.Name, })` writes the call's error to `_` and then uses `response` as if the call succeeded. When `json.Marshal` fails, `response` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `response` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line.
Discarded error (assigned to `_`, then its result used) backend/components/streams/streams_delete.go:65— `response, _ := json.Marshal(payloads.StreamsDeleteResponsePayload{ Name: expr.Name, })` writes the call's error to `_` and then uses `response` as if the call succeeded. When `json.Marshal` fails, `response` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `response` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line.
Discarded error (assigned to `_`, then its result used) backend/components/streams/streams_info.go:46— `response, _ := json.Marshal(res)` writes the call's error to `_` and then uses `response` as if the call succeeded. When `json.Marshal` fails, `response` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `response` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line.
Duplicated block (7 lines × 2) backend/components/communication/src/main/java/co/airy/core/communication/ConversationsController.java:148— backend/components/communication/src/main/java/co/airy/core/communication/ConversationsController.java:148-154 | backend/components/communication/src/main/java/co/airy/core/communication/ConversationsController.java:170-176 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. 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) backend/components/communication/src/main/java/co/airy/core/communication/ConversationsController.java:213— backend/components/communication/src/main/java/co/airy/core/communication/ConversationsController.java:213-219 | backend/components/communication/src/main/java/co/airy/core/communication/ConversationsController.java:255-261 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. 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) backend/components/communication/src/main/java/co/airy/core/communication/Stores.java:116— backend/components/communication/src/main/java/co/airy/core/communication/Stores.java:116-122 | backend/components/contacts/src/main/java/co/airy/core/contacts/Stores.java:169-176 — 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 `backend/components/communication/src/main/java/co/airy/core/communication/Stores.java:116` 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 (7 lines × 2) backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/WebhookController.java:37— backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/WebhookController.java:37-43 | backend/components/whatsapp/connector/src/main/java/co/airy/core/sources/whatsapp/WebhookController.java:41-47 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/Connector.java:76— backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/Connector.java:76-82 | backend/components/whatsapp/connector/src/main/java/co/airy/core/sources/whatsapp/Connector.java:62-68 — before extracting anything, compare `backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/Connector.java` and `backend/components/whatsapp/connector/src/main/java/co/airy/core/sources/whatsapp/Connector.java` 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. 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 `backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/Connector.java:76` 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 first that the copies are not typed on the same thing: `Api` names `co.airy.core.sources.facebook.api.Api` in one and `co.airy.core.sources.whatsapp.api.Api` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (7 lines × 2) REDACTED:129— REDACTED:129-135 | REDACTED:140-147 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:140` 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 (7 lines × 2) REDACTED:79— REDACTED:79-85 | REDACTED:257-263 — 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 `REDACTED:79` 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.
X2 · Cancellation propagation· Function without context.Context · ×7
Function without context.Context: post lib/go/httpclient/httpclient.go:28— `post` calls `http.NewRequest(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`.
Function without context.Context: getComponentsDetailsFromCloud REDACTED:61— `getComponentsDetailsFromCloud` calls `http.Get(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`.
Function without context.Context: sendFlinkSQL REDACTED:18— `sendFlinkSQL` calls `http.NewRequest(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`.
Function without context.Context: sendMessage REDACTED:137— `sendMessage` calls `http.NewRequest(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`.
Function without context.Context: sendFlinkSQLConfluent REDACTED:185— `sendFlinkSQLConfluent` calls `http.NewRequest(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`.
Function without context.Context: getFlinkResult REDACTED:235— `getFlinkResult` calls `http.NewRequest(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`.
Function without context.Context: getFlinkResultConfluent REDACTED:329— `getFlinkResultConfluent` calls `http.NewRequest(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`.
AC3 · Page structure· Page without a main landmark · ×6
Page without a main landmark frontend/chat-plugin/dev/development.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it.
Page without a main landmark frontend/control-center/development.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it.
Page without a main landmark frontend/control-center/index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it.
Page without a main landmark frontend/control-center/public/start.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark frontend/inbox/development.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it.
Page without a main landmark frontend/inbox/index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it.
Duplicated block (9 lines × 2) backend/components/admin/src/main/java/co/airy/core/admin/ChannelsController.java:108— backend/components/admin/src/main/java/co/airy/core/admin/ChannelsController.java:108-117 | backend/components/sources-api/src/main/java/co/airy/core/sources/api/ChannelsController.java:65-73 — 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 `backend/components/admin/src/main/java/co/airy/core/admin/ChannelsController.java:108` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (9 lines × 2) backend/components/chat-plugin/src/main/java/co/airy/core/chat_plugin/config/Jwt.java:66— backend/components/chat-plugin/src/main/java/co/airy/core/chat_plugin/config/Jwt.java:66-74 | lib/java/spring/auth/src/main/java/co/airy/spring/auth/Jwt.java:44-52 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `backend/components/chat-plugin/src/main/java/co/airy/core/chat_plugin/config/Jwt.java:66` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (9 lines × 2) backend/components/communication/src/main/java/co/airy/core/communication/ConversationsController.java:171— backend/components/communication/src/main/java/co/airy/core/communication/ConversationsController.java:171-179 | backend/components/communication/src/main/java/co/airy/core/communication/ConversationsController.java:214-222 — 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 `backend/components/communication/src/main/java/co/airy/core/communication/ConversationsController.java:171` 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) backend/components/sources-api/src/main/java/co/airy/core/sources/api/SourcesController.java:57— backend/components/sources-api/src/main/java/co/airy/core/sources/api/SourcesController.java:57-65 | backend/components/sources-api/src/main/java/co/airy/core/sources/api/SourcesController.java:84-92 — 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 `backend/components/sources-api/src/main/java/co/airy/core/sources/api/SourcesController.java: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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `backend/components/sources-api/src/main/java/co/airy/core/sources/api/SourcesController.java:56` calls `token`, `getToken` and `backend/components/sources-api/src/main/java/co/airy/core/sources/api/SourcesController.java:83` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 2) REDACTED:41— REDACTED:41-49 | REDACTED:215-223 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `REDACTED:212` calls `Add` and `REDACTED:38` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D12 · Dependency Hygiene· Dependency pinned to a stale untagged commit · ×4
Dependency pinned to a stale untagged commit: github.com/airyhq/airy — Direct dependency `github.com/airyhq/airy` is required at `v0.0.0-20220525151558-d1b9cb353828` in REDACTED — a pseudo-version, which pins an UNTAGGED commit from 2022-05-25, 4.5 years ago. The pin itself is exact, so this is not a reproducibility defect, and it is not a claim that the module is unmaintained. What it says is that this repository tracks no RELEASE of `github.com/airyhq/airy` and has not moved this requirement in 4.5 years: every fix the module has published since that commit — including any security fix — is absent from this build, whether the module went quiet or moved on without you. Check whether `github.com/airyhq/airy` now publishes tagged releases and move the requirement to one; if it publishes none, re-pin to a current commit.
Dependency pinned to a stale untagged commit: github.com/airyhq/airy/infrastructure/lib/go/k8s/util — Direct dependency `github.com/airyhq/airy/infrastructure/lib/go/k8s/util` is required at `v0.0.0-20220525151558-d1b9cb353828` in REDACTED — a pseudo-version, which pins an UNTAGGED commit from 2022-05-25, 4.5 years ago. The pin itself is exact, so this is not a reproducibility defect, and it is not a claim that the module is unmaintained. What it says is that this repository tracks no RELEASE of `github.com/airyhq/airy/infrastructure/lib/go/k8s/util` and has not moved this requirement in 4.5 years: every fix the module has published since that commit — including any security fix — is absent from this build, whether the module went quiet or moved on without you. Check whether `github.com/airyhq/airy/infrastructure/lib/go/k8s/util` now publishes tagged releases and move the requirement to one; if it publishes none, re-pin to a current commit.
Dependency pinned to a stale untagged commit: github.com/airyhq/airy — Direct dependency `github.com/airyhq/airy` is required at `v0.0.0-20220525151558-d1b9cb353828` in REDACTED — a pseudo-version, which pins an UNTAGGED commit from 2022-05-25, 4.5 years ago. The pin itself is exact, so this is not a reproducibility defect, and it is not a claim that the module is unmaintained. What it says is that this repository tracks no RELEASE of `github.com/airyhq/airy` and has not moved this requirement in 4.5 years: every fix the module has published since that commit — including any security fix — is absent from this build, whether the module went quiet or moved on without you. Check whether `github.com/airyhq/airy` now publishes tagged releases and move the requirement to one; if it publishes none, re-pin to a current commit.
Dependency pinned to a stale untagged commit: golang.org/x/mod — Direct dependency `golang.org/x/mod` is required at `v0.6.0-dev.0.20220106191415-9b9b3d81d5e3` in REDACTED — a pseudo-version, which pins an UNTAGGED commit from 2022-01-06, 4.9 years ago. The pin itself is exact, so this is not a reproducibility defect, and it is not a claim that the module is unmaintained. What it says is that this repository tracks no RELEASE of `golang.org/x/mod` and has not moved this requirement in 4.9 years: every fix the module has published since that commit — including any security fix — is absent from this build, whether the module went quiet or moved on without you. Check whether `golang.org/x/mod` now publishes tagged releases and move the requirement to one; if it publishes none, re-pin to a current commit.
Duplicated block (12 lines × 2) backend/components/chat-plugin/src/main/java/co/airy/core/chat_plugin/config/Jwt.java:77— backend/components/chat-plugin/src/main/java/co/airy/core/chat_plugin/config/Jwt.java:77-88 | backend/components/chat-plugin/src/main/java/co/airy/core/chat_plugin/config/Jwt.java:99-110 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `backend/components/chat-plugin/src/main/java/co/airy/core/chat_plugin/config/Jwt.java:77` 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) backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/Connector.java:60— backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/Connector.java:60-71 | backend/components/whatsapp/connector/src/main/java/co/airy/core/sources/whatsapp/Connector.java:49-60 — before extracting anything, compare `backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/Connector.java` and `backend/components/whatsapp/connector/src/main/java/co/airy/core/sources/whatsapp/Connector.java` 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. 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 `backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/Connector.java:60` 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 first that the copies are not typed on the same thing: `SendMessageRequest` names `co.airy.core.sources.facebook.dto.SendMessageRequest` in one and `co.airy.core.sources.whatsapp.dto.SendMessageRequest` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/Connector.java:58` calls `getConversation` and `backend/components/whatsapp/connector/src/main/java/co/airy/core/sources/whatsapp/Connector.java:47` 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 (12 lines × 2) backend/model/component/src/main/java/co/airy/model/component/Component.java:51— backend/model/component/src/main/java/co/airy/model/component/Component.java:51-62 | backend/model/contact/src/main/java/co/airy/model/contact/Contact.java:271-282 — 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) cli/pkg/cmd/api/endpoint.go:21— cli/pkg/cmd/api/endpoint.go:21-32 | cli/pkg/cmd/ui/ui.go:27-38 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) backend/components/admin/src/main/java/co/airy/core/admin/WebhooksController.java:162— backend/components/admin/src/main/java/co/airy/core/admin/WebhooksController.java:162-169 | backend/components/admin/src/main/java/co/airy/core/admin/WebhooksController.java:173-180 — 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 `backend/components/admin/src/main/java/co/airy/core/admin/WebhooksController.java:162` 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) backend/components/facebook/events-router/src/main/java/co/airy/core/sources/facebook/EventsRouter.java:113— backend/components/facebook/events-router/src/main/java/co/airy/core/sources/facebook/EventsRouter.java:113-120 | backend/components/whatsapp/events-router/src/main/java/co/airy/core/sources/whatsapp/EventsRouter.java:101-108 — 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 `backend/components/facebook/events-router/src/main/java/co/airy/core/sources/facebook/EventsRouter.java:113` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (8 lines × 2) lib/java/kafka/core/src/main/java/co/airy/kafka/core/deserializer/KafkaHybridDeserializer.java:35— lib/java/kafka/core/src/main/java/co/airy/kafka/core/deserializer/KafkaHybridDeserializer.java:35-43 | lib/java/kafka/core/src/main/java/co/airy/kafka/core/serializer/KafkaHybridSerializer.java:31-38 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `lib/java/kafka/core/src/main/java/co/airy/kafka/core/deserializer/KafkaHybridDeserializer.java:35` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (8 lines × 2) REDACTED:219— REDACTED:219-226 | REDACTED:342-349 — 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 `REDACTED:219` 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 first that the copies are not typed on the same thing: the declarations holding them bind `string` to `url` in one and `sessionID` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication· Edited copy of a member (25 corresponding lines) · ×3
Edited copy of a member (25 corresponding lines) backend/components/contacts/src/main/java/co/airy/core/contacts/ContactsController.java:46— backend/components/contacts/src/main/java/co/airy/core/contacts/ContactsController.java:46-70 | backend/components/contacts/src/main/java/co/airy/core/contacts/ContactsController.java:73-104 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (25 corresponding lines) backend/components/admin/src/main/java/co/airy/core/admin/ChannelsController.java:123— backend/components/admin/src/main/java/co/airy/core/admin/ChannelsController.java:123-147 | backend/components/sources-api/src/main/java/co/airy/core/sources/api/ChannelsController.java:91-116 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (25 corresponding lines) backend/components/admin/src/main/java/co/airy/core/admin/TimestampExtractor.java:11— backend/components/admin/src/main/java/co/airy/core/admin/TimestampExtractor.java:11-35 | backend/components/twilio/events-router/src/main/java/co/airy/core/sources/twilio/TimestampExtractor.java:13-40 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×3
Edited copy of a member (12 corresponding lines) backend/components/communication/src/main/java/co/airy/core/communication/MessagesController.java:54— backend/components/communication/src/main/java/co/airy/core/communication/MessagesController.java:54-74 | backend/components/contacts/src/main/java/co/airy/core/contacts/ConversationsController.java:67-78 — 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) backend/components/twilio/connector/src/main/java/co/airy/core/sources/twilio/ChannelsController.java:38— backend/components/twilio/connector/src/main/java/co/airy/core/sources/twilio/ChannelsController.java:38-49 | backend/components/twilio/connector/src/main/java/co/airy/core/sources/twilio/ChannelsController.java:52-64 — 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) backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/WebhookController.java:76— backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/WebhookController.java:76-87 | backend/components/whatsapp/connector/src/main/java/co/airy/core/sources/whatsapp/WebhookController.java:82-93 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (4 corresponding lines) · ×3
Edited copy of a member (4 corresponding lines) backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/api/Api.java:97— backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/api/Api.java:97-100 | backend/components/whatsapp/connector/src/main/java/co/airy/core/sources/whatsapp/api/Api.java:63-66 — 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) backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/api/Api.java:147— backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/api/Api.java:147-150 | backend/components/whatsapp/connector/src/main/java/co/airy/core/sources/whatsapp/api/Api.java:68-71 — 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) backend/model/event/src/main/java/co/airy/model/event/payload/ChannelUpdated.java:23— backend/model/event/src/main/java/co/airy/model/event/payload/ChannelUpdated.java:23-26 | backend/model/event/src/main/java/co/airy/model/event/payload/TagEvent.java:23-27 — 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 (16 lines × 2) backend/components/facebook/events-router/src/main/java/co/airy/core/sources/facebook/EventsRouter.java:82— backend/components/facebook/events-router/src/main/java/co/airy/core/sources/facebook/EventsRouter.java:82-97 | backend/components/whatsapp/events-router/src/main/java/co/airy/core/sources/whatsapp/EventsRouter.java:72-87 — 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 `backend/components/facebook/events-router/src/main/java/co/airy/core/sources/facebook/EventsRouter.java:82` 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 first that the copies are not typed on the same thing: `WebhookEvent` names `co.airy.core.sources.facebook.model.WebhookEvent` in one and `co.airy.core.sources.whatsapp.model.WebhookEvent` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (16 lines × 2) backend/components/viber/connector/src/main/java/co/airy/core/sources/viber/EventsRouter.java:38— backend/components/viber/connector/src/main/java/co/airy/core/sources/viber/EventsRouter.java:38-53 | backend/components/viber/connector/src/main/java/co/airy/core/sources/viber/EventsRouter.java:62-77 — 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 `backend/components/viber/connector/src/main/java/co/airy/core/sources/viber/EventsRouter.java:38` 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 (16 lines × 2) backend/model/component/src/main/java/co/airy/model/component/MetadataRepository.java:1— backend/model/component/src/main/java/co/airy/model/component/MetadataRepository.java:1-16 | backend/model/contact/src/main/java/co/airy/model/contact/MetadataRepository.java:1-16 — 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 `backend/model/component/src/main/java/co/airy/model/component/MetadataRepository.java:1` 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 (6 lines × 2) backend/components/webhook/consumer/src/main/java/co/airy/core/webhook/consumer/config/BeanstalkConsumerConfig.java:14— backend/components/webhook/consumer/src/main/java/co/airy/core/webhook/consumer/config/BeanstalkConsumerConfig.java:14-19 | backend/components/webhook/publisher/src/main/java/co/airy/core/webhook/publisher/config/BeanstalkProducerConfig.java:14-19 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) lib/java/spring/auth/src/main/java/co/airy/spring/auth/Jwt.java:38— lib/java/spring/auth/src/main/java/co/airy/spring/auth/Jwt.java:38-43 | lib/java/spring/auth/src/main/java/co/airy/spring/auth/Jwt.java:55-60 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note first that the copies are not typed on the same thing: the declarations holding them bind `auth` to `UserAuth` in one and `TokenAuth` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (6 lines × 2) backend/components/viber/connector/src/main/java/co/airy/core/sources/viber/config/Account.java:75— backend/components/viber/connector/src/main/java/co/airy/core/sources/viber/config/Account.java:75-80 | lib/java/spring/core/src/main/java/co/airy/spring/core/mappers/AiryObjectMapperConfig.java:15-20 — 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 (33 lines × 2 locations) frontend/chat-plugin/lib/src/config.ts:7— frontend/chat-plugin/lib/src/config.ts:7 · lib/typescript/model/ChatpluginConfig.ts:25 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.
Duplicated block (33 lines × 2 locations) frontend/control-center/src/pages/Streams/Creation/index.tsx:363— frontend/control-center/src/pages/Streams/Creation/index.tsx:363 · frontend/control-center/src/pages/Streams/Creation/index.tsx:407 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (33 lines × 2 locations) lib/typescript/render/providers/meta/MetaRender.tsx:301— lib/typescript/render/providers/meta/MetaRender.tsx:301 · lib/typescript/render/providers/meta/MetaRender.tsx:515 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Dead file (~89 LoC) frontend/chat-plugin/lib/src/airyRenderProps/AiryHeaderBar/index.tsx— no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (frontend/chat-plugin/lib/src/components/chat/index.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 (~89 LoC) lib/typescript/components/alerts/NotificationComponent/index.tsx— no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (lib/typescript/components/alerts/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~89 LoC) lib/typescript/model/ChatpluginConfig.ts— no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (lib/typescript/model/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~84 LoC) frontend/chat-plugin/lib/src/airyRenderProps/AiryInputBar/InputSelector/index.tsx— no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (frontend/chat-plugin/lib/src/airyRenderProps/AiryInputBar/index.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 (~84 LoC) lib/typescript/components/general/TabsPanel/index.tsx— no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (lib/typescript/components/general/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~84 LoC) lib/typescript/components/inputs/Dropdown/index.tsx— no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (lib/typescript/components/inputs/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
AC1 · Text alternatives· <canvas> without a text alternative · ×2
<canvas> without a text alternative frontend/inbox/src/pages/Inbox/MessageInput/AudioRecording/WaveformAudio.tsx:65— 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 lib/typescript/components/general/AudioClip/index.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.
AC2 · Forms & labels· <Input> field component without a label · ×2
<Input> field component without a label frontend/control-center/src/pages/Connectors/Providers/Airy/ChatPlugin/sections/CustomiseSection/ColorSection/SampleInput/index.tsx:15— 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 frontend/inbox/src/pages/Tags/index.tsx:163— 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.
SourceMessagePreview.SourceMessagePreview::lastMessageIsIcon (cyclomatic 33) lib/typescript/render/SourceMessagePreview.tsx:158— SourceMessagePreview.SourceMessagePreview::lastMessageIsIcon has cyclomatic complexity 33 (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. This shape REPEATS in the file: one other method here (SourceMessagePreview.SourceMessagePreview::lastMessageIsText) 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.
SourceMessagePreview.SourceMessagePreview::lastMessageIsText (cyclomatic 30) lib/typescript/render/SourceMessagePreview.tsx:48— SourceMessagePreview.SourceMessagePreview::lastMessageIsText has cyclomatic complexity 30 (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 (SourceMessagePreview.SourceMessagePreview::lastMessageIsIcon) 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.
main.main (cyclomatic 16) REDACTED:15— main.main has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 5 of the 16 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 85, 42, 54). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
main.main (cyclomatic 16) REDACTED:14— main.main has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 5 of the 16 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 85, 42, 54). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
Deprecated module: github.com/aws/aws-sdk-go — `github.com/aws/aws-sdk-go` is required at v1.44.122 in REDACTED, and its author has DEPRECATED the module: "aws-sdk-go is deprecated. Use aws-sdk-go-v2. See https://aws.amazon.com/blogs/developer/announcing-end-of-support-for-aws-sdk-for-go-v1-on-july-31-2025/." A deprecation is declared by the author in the module's own REDACTED and applies to the whole module, not to one release, so moving to a newer version of it does not clear this. Follow the replacement the notice names.
Deprecated module: github.com/aws/aws-sdk-go — `github.com/aws/aws-sdk-go` is required at v1.44.122 in REDACTED, and its author has DEPRECATED the module: "aws-sdk-go is deprecated. Use aws-sdk-go-v2. See https://aws.amazon.com/blogs/developer/announcing-end-of-support-for-aws-sdk-for-go-v1-on-july-31-2025/." A deprecation is declared by the author in the module's own REDACTED and applies to the whole module, not to one release, so moving to a newer version of it does not clear this. Follow the replacement the notice names.
main.main (cognitive 46) REDACTED:15— main.main has cognitive complexity 46 (threshold 15). Drivers by points: if/else 15 (42 pts), match/switch 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 28). Most of this is not in the body itself: 3 of the 46 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 85, 42, 54). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
main.main (cognitive 46) REDACTED:14— main.main has cognitive complexity 46 (threshold 15). Drivers by points: if/else 15 (42 pts), match/switch 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 28). Most of this is not in the body itself: 3 of the 46 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 85, 42, 54). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
SourceMessagePreview.SourceMessagePreview::lastMessageIsText (cognitive 28) lib/typescript/render/SourceMessagePreview.tsx:48— SourceMessagePreview.SourceMessagePreview::lastMessageIsText has cognitive complexity 28 (threshold 15). Drivers by points: if/else 15 (16 pts), boolean chains 12 (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. This shape REPEATS in the file: one other method here (SourceMessagePreview.SourceMessagePreview::lastMessageIsIcon) 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.
SourceMessagePreview.SourceMessagePreview::lastMessageIsIcon (cognitive 26) lib/typescript/render/SourceMessagePreview.tsx:158— SourceMessagePreview.SourceMessagePreview::lastMessageIsIcon has cognitive complexity 26 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 10 (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. This shape REPEATS in the file: one other method here (SourceMessagePreview.SourceMessagePreview::lastMessageIsText) 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.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (5 members, 50+ identical tokens) backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/Stores.java:144— backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/Stores.java:144-151 | backend/components/google/connector/src/main/java/co/airy/core/sources/google/Stores.java:93-100 | backend/components/twilio/connector/src/main/java/co/airy/core/sources/twilio/Stores.java:111-118 | backend/components/viber/connector/src/main/java/co/airy/core/sources/viber/Stores.java:117-124 | backend/components/whatsapp/connector/src/main/java/co/airy/core/sources/whatsapp/Stores.java:137-144 — These 5 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 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.
Members sharing a duplicated core (5 members, 50+ identical tokens) backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/WebhookController.java:36— backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/WebhookController.java:36-48 | backend/components/google/connector/src/main/java/co/airy/core/sources/google/WebhookController.java:37-48 | backend/components/twilio/connector/src/main/java/co/airy/core/sources/twilio/WebhookController.java:40-50 | backend/components/viber/connector/src/main/java/co/airy/core/sources/viber/WebhookController.java:36-48 | backend/components/whatsapp/connector/src/main/java/co/airy/core/sources/whatsapp/WebhookController.java:40-52 — These 5 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 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 (17 corresponding lines) · ×2
Edited copy of a member (17 corresponding lines) backend/components/admin/src/main/java/co/airy/core/admin/UsersController.java:29— backend/components/admin/src/main/java/co/airy/core/admin/UsersController.java:29-45 | backend/components/contacts/src/main/java/co/airy/core/contacts/ContactsController.java:107-127 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) backend/components/twilio/connector/src/main/java/co/airy/core/sources/twilio/WebhookController.java:90— backend/components/twilio/connector/src/main/java/co/airy/core/sources/twilio/WebhookController.java:90-106 | lib/java/url/src/main/java/co/airy/url/UrlUtil.java:12-28 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×2
Edited copy of a member (18 corresponding lines) backend/components/contacts/src/main/java/co/airy/core/contacts/payload/ContactResponsePayload.java:33— backend/components/contacts/src/main/java/co/airy/core/contacts/payload/ContactResponsePayload.java:33-50 | backend/components/contacts/src/main/java/co/airy/core/contacts/payload/ContactWithMergeHistoryResponsePayload.java:39-61 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) infrastructure/lib/go/k8s/handler/deployments.go:67— infrastructure/lib/go/k8s/handler/deployments.go:67-86 | infrastructure/lib/go/k8s/handler/deployments.go:95-112 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×2
Edited copy of a member (11 corresponding lines) lib/go/k8s/configmaps.go:76— lib/go/k8s/configmaps.go:76-86 | lib/go/k8s/configmaps.go:93-110 — 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) backend/model/event/src/main/java/co/airy/model/event/payload/ComponentUpdated.java:42— backend/model/event/src/main/java/co/airy/model/event/payload/ComponentUpdated.java:42-52 | backend/model/event/src/main/java/co/airy/model/event/payload/MetadataUpdated.java:42-53 — 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 (8 corresponding lines) · ×2
Edited copy of a member (8 corresponding lines) backend/components/sources-api/src/main/java/co/airy/core/sources/api/Stores.java:171— backend/components/sources-api/src/main/java/co/airy/core/sources/api/Stores.java:171-178 | backend/components/sources-api/src/main/java/co/airy/core/sources/api/Stores.java:189-196 — 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) backend/components/admin/src/main/java/co/airy/core/admin/TagsController.java:83— backend/components/admin/src/main/java/co/airy/core/admin/TagsController.java:83-91 | backend/components/admin/src/main/java/co/airy/core/admin/TemplatesController.java:64-71 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 9+ corresponding lines) · ×2
Edited copies of one member (3 members, 9+ corresponding lines) backend/components/cognigy/src/main/java/co/airy/core/cognigy_connector/CognigyClientConfig.java:14— backend/components/cognigy/src/main/java/co/airy/core/cognigy_connector/CognigyClientConfig.java:14-22 | backend/components/ibm-watson-assistant/src/main/java/co/airy/core/ibm_watson_assistant_connector/IbmWatsonAssistantClientConfig.java:17-27 | backend/components/rasa/src/main/java/co/airy/core/rasa_connector/RasaClientConfig.java:15-23 — 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.
Edited copies of one member (3 members, 9+ corresponding lines) backend/components/admin/src/main/java/co/airy/core/admin/WebhooksController.java:160— backend/components/admin/src/main/java/co/airy/core/admin/WebhooksController.java:160-169 | backend/components/admin/src/main/java/co/airy/core/admin/WebhooksController.java:171-180 | backend/components/admin/src/main/java/co/airy/core/admin/payload/UserResponsePayload.java:18-26 — 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.
Duplicated block (5 lines × 2) backend/components/admin/src/main/java/co/airy/core/admin/Stores.java:74— backend/components/admin/src/main/java/co/airy/core/admin/Stores.java:74-78 | backend/components/sources-api/src/main/java/co/airy/core/sources/api/Stores.java:67-71 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) backend/components/admin/src/main/java/co/airy/core/admin/Stores.java:141— backend/components/admin/src/main/java/co/airy/core/admin/Stores.java:141-145 | backend/components/sources-api/src/main/java/co/airy/core/sources/api/Stores.java:152-156 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (13 lines × 3) cli/pkg/providers/aws/aws.go:44— cli/pkg/providers/aws/aws.go:44-56 | cli/pkg/providers/gcp/gcp.go:44-56 | cli/pkg/providers/minikube/minikube.go:54-66 — `cli/pkg/providers/aws/aws.go` and `cli/pkg/providers/gcp/gcp.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 2 separate duplicated blocks between them, totalling at least 26 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `cli/pkg/providers/aws/aws.go:44` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13 lines × 3) cli/pkg/providers/aws/aws.go:71— cli/pkg/providers/aws/aws.go:71-83 | cli/pkg/providers/gcp/gcp.go:71-83 | cli/pkg/providers/minikube/minikube.go:75-87 — `cli/pkg/providers/aws/aws.go` and `cli/pkg/providers/gcp/gcp.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 2 separate duplicated blocks between them, totalling at least 26 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `cli/pkg/providers/aws/aws.go:71` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Off the main sequence: github.com/airyhq/airy/infrastructure/lib/go/k8s/util — github.com/airyhq/airy/infrastructure/lib/go/k8s/util: 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: github.com/airyhq/airy/lib/go/httpclient — github.com/airyhq/airy/lib/go/httpclient: 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.
Fake-async — async method never awaits REDACTED:237— `startHealthcheck` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits REDACTED:256— `main` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
IC1 · Incompleteness & stubs· Both branches are identical · ×2
Both branches are identical — the condition decides nothing frontend/control-center/src/pages/Connectors/Providers/Airy/ChatPlugin/sections/InstallSection/InstallSection.tsx:52— Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
Both branches are identical — the condition decides nothing frontend/inbox/src/services/format/date.ts:16— The `if` and its `else` contain the same statements, so no input can make the condition matter. Implement the distinction that was intended, or drop the branch and keep the body.
R10 · Code Duplication· Duplicated block with local edits (60 matched lines × 2 locations) · ×2
Duplicated block with local edits (60 matched lines × 2 locations) frontend/control-center/src/pages/Connectors/ConnectedChannelsList/ChannelsListItem/index.tsx:17— frontend/control-center/src/pages/Connectors/ConnectedChannelsList/ChannelsListItem/index.tsx:17 · frontend/control-center/src/pages/Inbox/ChannelsList/ChannelListItem/index.tsx:16 — the two spans are one implementation copied and then locally edited — 404 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) frontend/control-center/src/pages/Connectors/Providers/Viber/ViberConnect.tsx:13— frontend/control-center/src/pages/Connectors/Providers/Viber/ViberConnect.tsx:13 · frontend/control-center/src/pages/Connectors/Providers/WhatsappBusinessCloud/WhatsappConnect.tsx:13 — the two spans are one implementation copied and then locally edited — 425 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 (27 lines × 2 locations) frontend/control-center/src/pages/Schemas/ListMode/ListMode.tsx:52— frontend/control-center/src/pages/Schemas/ListMode/ListMode.tsx:52 · frontend/control-center/src/pages/Status/index.tsx:51 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (27 lines × 2 locations) frontend/inbox/src/components/Dialog/index.tsx:17— frontend/inbox/src/components/Dialog/index.tsx:17 · frontend/inbox/src/components/DialogCustomizable/index.tsx:23 — 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.
Dead file (~117 LoC) frontend/chat-plugin/lib/src/api/index.tsx— no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (frontend/chat-plugin/lib/src/airyRenderProps/AiryInputBar/index.tsx, frontend/chat-plugin/lib/src/components/chat/index.tsx, frontend/chat-plugin/lib/src/websocket/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~117 LoC) lib/typescript/components/general/FilterBar/index.tsx— no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (lib/typescript/components/general/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~100 LoC) lib/typescript/components/cta/SmartButton/index.tsx— no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (lib/typescript/components/cta/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~100 LoC) lib/typescript/render/providers/google/components/Suggestions/index.tsx— no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (lib/typescript/render/providers/google/GoogleRender.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
Swallowed exception (empty catch) lib/java/spring/web/src/main/java/co/airy/spring/web/filters/RequestLoggingFilter.java:76— 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) backend/model/metadata/src/main/java/co/airy/model/metadata/MetadataObjectMapper.java:81— 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.
AC1 · Text alternatives· <video> without a captions track · ×1
<video> without a captions track lib/typescript/render/components/Video/index.tsx:36— 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).
Low contrast colour pair in CSS (4.4:1) frontend/control-center/public/start.html:78— `.boxButton` sets color: white on background-color: #1578D4 — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
index.ConnectorConfig (cyclomatic 51) frontend/control-center/src/pages/Connectors/ConnectorConfig/index.tsx:38— index.ConnectorConfig has cyclomatic complexity 51 (threshold 15). Of this number, 29 points are the body's own statements and 22 belong to 3 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.
InputOptions.InputOptions (cyclomatic 50) frontend/inbox/src/pages/Inbox/MessageInput/InputOptions.tsx:41— InputOptions.InputOptions has cyclomatic complexity 50 (threshold 15). Of this number, 39 points are the body's own statements and 11 belong to 5 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.
index.ContactDetails (cyclomatic 48) frontend/inbox/src/components/ContactDetails/index.tsx:44— index.ContactDetails has cyclomatic complexity 48 (threshold 15). Of this number, 18 points are the body's own statements and 30 belong to 10 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.
CustomiseSection.CustomiseSection (cyclomatic 47) frontend/control-center/src/pages/Connectors/Providers/Airy/ChatPlugin/sections/CustomiseSection/CustomiseSection.tsx:23— CustomiseSection.CustomiseSection has cyclomatic complexity 47 (threshold 15). Of this number, 41 points are the body's own statements and 6 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.
index.Sidebar (cyclomatic 42) frontend/control-center/src/components/Sidebar/index.tsx:41— index.Sidebar has cyclomatic complexity 42 (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.
MetaRender.metaOutbound (cyclomatic 42) lib/typescript/render/providers/meta/MetaRender.tsx:342— MetaRender.metaOutbound 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.
index.ColorSection (cyclomatic 41) frontend/control-center/src/pages/Connectors/Providers/Airy/ChatPlugin/sections/CustomiseSection/ColorSection/index.tsx:36— index.ColorSection has cyclomatic complexity 41 (threshold 15). Of this number, 31 points are the body's own statements and 10 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.
index.Catalog (cyclomatic 39) frontend/control-center/src/pages/Catalog/index.tsx:30— index.Catalog has cyclomatic complexity 39 (threshold 15). Most of this is not in the body itself: 8 of the 39 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 89, a function literal at line 174, a function literal at line 50, …). 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.
index.MessageList (cyclomatic 36) frontend/inbox/src/pages/Inbox/Messenger/MessageList/index.tsx:29— index.MessageList has cyclomatic complexity 36 (threshold 15). Most of this is not in the body itself: 2 of the 36 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 70, a function literal at line 52, a function literal at line 119, …). 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.
index.Chat (cyclomatic 35) frontend/chat-plugin/lib/src/components/chat/index.tsx:56— index.Chat has cyclomatic complexity 35 (threshold 15). Most of this is not in the body itself: 13 of the 35 points are its own statements and the rest belongs to 12 function items inside it that branch (a function literal at line 91, chatHiddenInitialState, styleFor, …). 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.
FacebookConnect.FacebookConnect (cyclomatic 33) frontend/control-center/src/pages/Connectors/Providers/Facebook/Messenger/FacebookConnect.tsx:23— FacebookConnect.FacebookConnect has cyclomatic complexity 33 (threshold 15). Of this number, 17 points are the body's own statements and 16 belong to 5 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.
index.SubscriptionModal (cyclomatic 32) frontend/control-center/src/pages/Webhooks/SubscriptionModal/index.tsx:24— index.SubscriptionModal has cyclomatic complexity 32 (threshold 15). Most of this is not in the body itself: 14 of the 32 points are its own statements and the rest belongs to 3 function items inside it that branch (handleChecked, upsertWebhook, getButtonTitle). 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.
ItemInfo.ItemInfo (cyclomatic 31) frontend/control-center/src/pages/Status/ComponentListItem/ItemInfo.tsx:31— ItemInfo.ItemInfo has cyclomatic complexity 31 (threshold 15). Of this number, 24 points are the body's own statements and 7 belong to 2 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.
index.InputToggleSection (cyclomatic 31) REDACTED:40— index.InputToggleSection has cyclomatic complexity 31 (threshold 15). Of this number, 25 points are the body's own statements and 6 belong to 4 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.
WhatsappConnect.WhatsappConnect (cyclomatic 31) frontend/control-center/src/pages/Connectors/Providers/WhatsappBusinessCloud/WhatsappConnect.tsx:23— WhatsappConnect.WhatsappConnect has cyclomatic complexity 31 (threshold 15). Of this number, 17 points are the body's own statements and 14 belong to 5 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.
index.Creation (cyclomatic 31) frontend/control-center/src/pages/Streams/Creation/index.tsx:31— index.Creation has cyclomatic complexity 31 (threshold 15). Of this number, 17 points are the body's own statements and 14 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.
MetaRender.render (cyclomatic 31) lib/typescript/render/providers/meta/MetaRender.tsx:37— MetaRender.render has cyclomatic complexity 31 (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.
index.AiryInputBar (cyclomatic 30) frontend/chat-plugin/lib/src/airyRenderProps/AiryInputBar/index.tsx:26— index.AiryInputBar has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 10 of the 30 points are its own statements and the rest belongs to 13 function items inside it that branch (AttachmentInput::acceptedFileTypes, onSubmit, handleKeyDown, …). 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.
index.ConnectorWrapper (cyclomatic 30) frontend/control-center/src/pages/Connectors/ConnectorWrapper/index.tsx:38— index.ConnectorWrapper has cyclomatic complexity 30 (threshold 15). Of this number, 15 points are the body's own statements and 15 belong to 6 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
GoogleConnect.GoogleConnect (cyclomatic 29) frontend/control-center/src/pages/Connectors/Providers/Google/GoogleConnect.tsx:27— GoogleConnect.GoogleConnect has cyclomatic complexity 29 (threshold 15). Of this number, 16 points are the body's own statements and 13 belong to 6 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
TwilioConnect.TwilioConnect (cyclomatic 29) frontend/control-center/src/pages/Connectors/Providers/Twilio/TwilioConnect.tsx:28— TwilioConnect.TwilioConnect has cyclomatic complexity 29 (threshold 15). 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 (buttonStatus, connectTwilioChannel, a function literal at line 47, …). 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.
index.EnrichedSchemaSection (cyclomatic 29) frontend/control-center/src/pages/Schemas/SchemaItem/SchemaDescription/EnrichedSchemaSection/index.tsx:32— index.EnrichedSchemaSection has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 6 of the 29 points are its own statements and the rest belongs to 12 function items inside it that branch (a function literal at line 97, a function literal at line 116, recalculateContainerHeight, …). 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.
index.CatalogCard (cyclomatic 26) frontend/control-center/src/pages/Catalog/CatalogCard/index.tsx:49— index.CatalogCard has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 11 of the 26 points are its own statements and the rest belongs to 5 function items inside it that branch (CatalogCardButton, a function literal at line 79, handleCardClick, …). 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.
Popup.PopUpFilter (cyclomatic 26) frontend/inbox/src/pages/Inbox/QuickFilter/Popup.tsx:46— Popup.PopUpFilter has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 11 of the 26 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 97, toggleTag, a function literal at line 227, …). 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.
InstagramConnect.InstagramConnect (cyclomatic 25) frontend/control-center/src/pages/Connectors/Providers/Instagram/InstagramConnect.tsx:17— InstagramConnect.InstagramConnect has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 12 of the 25 points are its own statements and the rest belongs to 3 function items inside it that branch (buttonStatus, connectNewChannel, a function literal at line 43). 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.
index.ConversationMetadata (cyclomatic 24) frontend/inbox/src/pages/Inbox/Messenger/ConversationMetadata/index.tsx:55— index.ConversationMetadata has cyclomatic complexity 24 (threshold 15). Of this number, 12 points are the body's own statements and 12 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.
MetaRender.metaInbound (cyclomatic 24) lib/typescript/render/providers/meta/MetaRender.tsx:220— MetaRender.metaInbound 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.
ChatPluginRender.mapContent (cyclomatic 24) lib/typescript/render/providers/chatplugin/ChatPluginRender.tsx:79— ChatPluginRender.mapContent 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.
TwilioRender.inboundContent (cyclomatic 24) lib/typescript/render/providers/twilio/TwilioRender.tsx:50— TwilioRender.inboundContent 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.
index.TopBar (cyclomatic 23) frontend/control-center/src/components/TopBar/index.tsx:37— index.TopBar has cyclomatic complexity 23 (threshold 15). Of this number, 18 points are the body's own statements and 5 belong to 2 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.
ViberConnect.ViberConnect (cyclomatic 23) frontend/control-center/src/pages/Connectors/Providers/Viber/ViberConnect.tsx:23— ViberConnect.ViberConnect has cyclomatic complexity 23 (threshold 15). Of this number, 14 points are the body's own statements and 9 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.
index.SchemaSection (cyclomatic 23) frontend/control-center/src/pages/Schemas/SchemaItem/SchemaDescription/SchemaSection/index.tsx:33— index.SchemaSection has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 6 of the 23 points are its own statements and the rest belongs to 7 function items inside it that branch (recalculateContainerHeight, a function literal at line 100, a function literal at line 166, …). 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.
index.MessageInput::sendMessage (cyclomatic 23) frontend/inbox/src/pages/Inbox/MessageInput/index.tsx:234— index.MessageInput::sendMessage 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. This shape REPEATS in the file: one other method here (index.MessageInput) 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.
index.MessengerContainer (cyclomatic 23) frontend/inbox/src/pages/Inbox/Messenger/MessengerContainer/index.tsx:30— index.MessengerContainer has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 6 of the 23 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 42, a function literal at line 100, handleDragLeave, …). 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.
ChatPluginConnect.ChatPluginConnect (cyclomatic 22) frontend/control-center/src/pages/Connectors/Providers/Airy/ChatPlugin/ChatPluginConnect.tsx:46— ChatPluginConnect.ChatPluginConnect has cyclomatic complexity 22 (threshold 15). Of this number, 14 points are the body's own statements and 8 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.
index.TopBar (cyclomatic 22) frontend/inbox/src/components/TopBar/index.tsx:38— index.TopBar has cyclomatic complexity 22 (threshold 15). Of this number, 17 points are the body's own statements and 5 belong to 2 function items inside it that branch. 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.
index.MessageInput (cyclomatic 22) frontend/inbox/src/pages/Inbox/MessageInput/index.tsx:58— index.MessageInput 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. This shape REPEATS in the file: one other method here (index.MessageInput::sendMessage) 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.
index.allReducer (cyclomatic 20) frontend/inbox/src/reducers/data/conversations/index.ts:184— index.allReducer has cyclomatic complexity 20 (threshold 15). Of this number, 18 points are the body's own statements and 2 belong to 2 function items inside it that branch. 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.
index.NotificationComponent (cyclomatic 20) lib/typescript/components/alerts/NotificationComponent/index.tsx:23— index.NotificationComponent has cyclomatic complexity 20 (threshold 15). Of this number, 12 points are the body's own statements and 8 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.
InstallSection.InstallSection::getTemplateConfig (cyclomatic 19) frontend/control-center/src/pages/Connectors/Providers/Airy/ChatPlugin/sections/InstallSection/InstallSection.tsx:49— InstallSection.InstallSection::getTemplateConfig has cyclomatic complexity 19 (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.
TopicDescription.TopicDescription (cyclomatic 19) frontend/control-center/src/pages/Topics/TopicItem/TopicDescription/TopicDescription.tsx:14— TopicDescription.TopicDescription has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 7 of the 19 points are its own statements and the rest belongs to 5 function items inside it that branch (recalculateContainerHeight, calculateRetentionTime, calculateRetentionSize, …). 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.
ContactInfoPoint.ContactInfoPoint (cyclomatic 19) frontend/inbox/src/components/ContactDetails/ContactInfoPoint.tsx:24— ContactInfoPoint.ContactInfoPoint 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 3 function items inside it that branch (handleChange, InfoValue, getDisplayedtext). 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.
index.AudioRecording (cyclomatic 19) frontend/inbox/src/pages/Inbox/MessageInput/AudioRecording/index.tsx:34— index.AudioRecording has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 8 of the 19 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 107, 76, 139, …). 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.
index.Suggestions (cyclomatic 19) lib/typescript/render/providers/google/components/Suggestions/index.tsx:23— index.Suggestions has cyclomatic complexity 19 (threshold 15). Of this number, 11 points are the body's own statements and 8 belong 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.
index.ConnectedChannelsList (cyclomatic 18) frontend/control-center/src/pages/Connectors/ConnectedChannelsList/index.tsx:39— index.ConnectedChannelsList 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, 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.
index.ConversationList (cyclomatic 18) frontend/inbox/src/pages/Inbox/ConversationList/index.tsx:38— index.ConversationList has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 7 of the 18 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 69, hasPreviousMessages, a function literal at line 64). 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.
InputComponent.render (cyclomatic 18) lib/typescript/components/inputs/Input/index.tsx:260— InputComponent.render has cyclomatic complexity 18 (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.
GoogleRender.googleInbound (cyclomatic 18) lib/typescript/render/providers/google/GoogleRender.tsx:60— GoogleRender.googleInbound 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.
Contact.toMetadata (cyclomatic 17) backend/model/contact/src/main/java/co/airy/model/contact/Contact.java:216— Contact.toMetadata 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.
main.getFlinkResultConfluent (cyclomatic 17) REDACTED:329— main.getFlinkResultConfluent 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.
handler.getContainerWithEnvReference (cyclomatic 17) infrastructure/lib/go/k8s/handler/containers.go:52— handler.getContainerWithEnvReference 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.
index.CatalogItemDetails::SideColumnContent (cyclomatic 17) frontend/control-center/src/pages/Catalog/CatalogItemDetails/index.tsx:184— index.CatalogItemDetails::SideColumnContent 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.
TableRow.TableRowComponent (cyclomatic 17) frontend/inbox/src/pages/Tags/TableRow.tsx:25— TableRow.TableRowComponent 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 literals inside it that branch (lines 78, 44, 99). 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.
index.Carousel (cyclomatic 17) lib/typescript/components/general/Carousel/index.tsx:7— index.Carousel 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 5 function items inside it that branch (a function literal at line 88, maximumScrollRight, maximumScrollLeft, …). 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.
handler.getVolumeMountName (cyclomatic 16) infrastructure/lib/go/k8s/handler/containers.go:7— handler.getVolumeMountName 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.
index.IconChannel (cyclomatic 16) frontend/inbox/src/components/IconChannel/index.tsx:87— index.IconChannel has cyclomatic complexity 16 (threshold 15). Of this number, 14 points are the body's own statements and 2 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.
index.Tooltip (cyclomatic 16) lib/typescript/components/tooltip/index.tsx:20— index.Tooltip has cyclomatic complexity 16 (threshold 15). Of this number, 15 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.
MetaRender.metaOutbound (cognitive 56) lib/typescript/render/providers/meta/MetaRender.tsx:342— MetaRender.metaOutbound has cognitive complexity 56 (threshold 15). Drivers by points: if/else 28 (38 pts), boolean chains 13, ternaries 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.
index.ContactDetails (cognitive 49) frontend/inbox/src/components/ContactDetails/index.tsx:44— index.ContactDetails has cognitive complexity 49 (threshold 15). Drivers by points: boolean chains 25, if/else 19 (22 pts), ternaries 2 (nesting depth added 3). Most of this is not in the body itself: 14 of the 49 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 119, removeDefaultTextWhenEditing, 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.
index.Catalog (cognitive 47) frontend/control-center/src/pages/Catalog/index.tsx:30— index.Catalog has cognitive complexity 47 (threshold 15). Drivers by points: if/else 12 (15 pts), ternaries 7 (15 pts), boolean chains 14, match/switch 1 (2 pts), loops 1 (nesting depth added 12). Most of this is not in the body itself: 8 of the 47 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 89, a function literal at line 174, a function literal at line 75, …). 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.
index.Tooltip (cognitive 43) lib/typescript/components/tooltip/index.tsx:20— index.Tooltip has cognitive complexity 43 (threshold 15). Drivers by points: ternaries 8 (36 pts), boolean chains 7 (nesting depth added 28). Of this number, 42 points are the body's own statements and 1 belongs to one function item 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.
index.Sidebar (cognitive 40) frontend/control-center/src/components/Sidebar/index.tsx:41— index.Sidebar has cognitive complexity 40 (threshold 15). Drivers by points: ternaries 33, boolean chains 7. 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.
CustomiseSection.CustomiseSection (cognitive 39) frontend/control-center/src/pages/Connectors/Providers/Airy/ChatPlugin/sections/CustomiseSection/CustomiseSection.tsx:23— CustomiseSection.CustomiseSection has cognitive complexity 39 (threshold 15). Drivers by points: boolean chains 36, ternaries 3. Of this number, 35 points are the body's own statements and 4 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.
index.EnrichedSchemaSection (cognitive 39) frontend/control-center/src/pages/Schemas/SchemaItem/SchemaDescription/EnrichedSchemaSection/index.tsx:32— index.EnrichedSchemaSection has cognitive complexity 39 (threshold 15). Drivers by points: if/else 19 (27 pts), boolean chains 8, ternaries 2 (3 pts), error handling 1 (nesting depth added 9). Most of this is not in the body itself: 5 of the 39 points are its own statements and the rest belongs to 12 function items inside it that branch (a function literal at line 97, a function literal at line 116, a function literal at line 227, …). 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.
handler.getVolumeMountName (cognitive 38) infrastructure/lib/go/k8s/handler/containers.go:7— handler.getVolumeMountName has cognitive complexity 38 (threshold 15). Drivers by points: if/else 8 (25 pts), loops 3 (9 pts), boolean chains 4 (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.
index.SubscriptionModal (cognitive 36) frontend/control-center/src/pages/Webhooks/SubscriptionModal/index.tsx:24— index.SubscriptionModal has cognitive complexity 36 (threshold 15). Drivers by points: boolean chains 14, ternaries 8 (12 pts), if/else 7 (9 pts), match/switch 1 (nesting depth added 6). Most of this is not in the body itself: 12 of the 36 points are its own statements and the rest belongs to 3 function items inside it that branch (handleChecked, getButtonTitle, upsertWebhook). 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.
main.getFlinkResultConfluent (cognitive 32) REDACTED:329— main.getFlinkResultConfluent has cognitive complexity 32 (threshold 15). Drivers by points: if/else 17 (31 pts), boolean chains 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
index.Chat (cognitive 32) frontend/chat-plugin/lib/src/components/chat/index.tsx:56— index.Chat has cognitive complexity 32 (threshold 15). Drivers by points: if/else 13, boolean chains 10, ternaries 7 (8 pts), match/switch 1 (nesting depth added 1). Most of this is not in the body itself: 12 of the 32 points are its own statements and the rest belongs to 12 function items inside it that branch (a function literal at line 91, chatHiddenInitialState, a function literal at line 138, …). 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.
index.ColorSection (cognitive 31) frontend/control-center/src/pages/Connectors/Providers/Airy/ChatPlugin/sections/CustomiseSection/ColorSection/index.tsx:36— index.ColorSection has cognitive complexity 31 (threshold 15). Drivers by points: boolean chains 30, match/switch 1. Of this number, 30 points are the body's own statements and 1 belongs to one function item 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.
MetaRender.metaInbound (cognitive 31) lib/typescript/render/providers/meta/MetaRender.tsx:220— MetaRender.metaInbound has cognitive complexity 31 (threshold 15). Drivers by points: if/else 14 (19 pts), boolean chains 7, ternaries 2 (5 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.
index.InputToggleSection (cognitive 30) REDACTED:40— index.InputToggleSection has cognitive complexity 30 (threshold 15). Drivers by points: boolean chains 23, if/else 6, ternaries 1. Of this number, 24 points are the body's own statements and 6 belong to 4 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.
InputOptions.InputOptions (cognitive 30) frontend/inbox/src/pages/Inbox/MessageInput/InputOptions.tsx:41— InputOptions.InputOptions has cognitive complexity 30 (threshold 15). Drivers by points: boolean chains 20, if/else 8 (9 pts), ternaries 1 (nesting depth added 1). Of this number, 17 points are the body's own statements and 13 belong to 5 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.
index.MessageInput::sendMessage (cognitive 29) frontend/inbox/src/pages/Inbox/MessageInput/index.tsx:234— index.MessageInput::sendMessage has cognitive complexity 29 (threshold 15). Drivers by points: if/else 8 (21 pts), boolean chains 6, match/switch 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.
TwilioRender.inboundContent (cognitive 29) lib/typescript/render/providers/twilio/TwilioRender.tsx:50— TwilioRender.inboundContent has cognitive complexity 29 (threshold 15). Drivers by points: if/else 13 (19 pts), boolean chains 10 (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.
TwilioConnect.TwilioConnect (cognitive 28) frontend/control-center/src/pages/Connectors/Providers/Twilio/TwilioConnect.tsx:28— TwilioConnect.TwilioConnect has cognitive complexity 28 (threshold 15). Drivers by points: boolean chains 15, ternaries 6 (9 pts), if/else 4 (nesting depth added 3). Most of this is not in the body itself: 11 of the 28 points are its own statements and the rest belongs to 6 function items inside it that branch (connectTwilioChannel, a function literal at line 47, buttonStatus, …). 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.
index.SchemaSection (cognitive 28) frontend/control-center/src/pages/Schemas/SchemaItem/SchemaDescription/SchemaSection/index.tsx:33— index.SchemaSection has cognitive complexity 28 (threshold 15). Drivers by points: if/else 16 (20 pts), boolean chains 7, ternaries 1 (nesting depth added 4). Most of this is not in the body itself: 4 of the 28 points are its own statements and the rest belongs to 7 function items inside it that branch (recalculateContainerHeight, a function literal at line 100, a function literal at line 166, …). 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.
ChatPluginRender.mapContent (cognitive 28) lib/typescript/render/providers/chatplugin/ChatPluginRender.tsx:79— ChatPluginRender.mapContent has cognitive complexity 28 (threshold 15). Drivers by points: if/else 17 (20 pts), boolean chains 8 (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.
index.MessageList (cognitive 27) frontend/inbox/src/pages/Inbox/Messenger/MessageList/index.tsx:29— index.MessageList has cognitive complexity 27 (threshold 15). Drivers by points: if/else 12 (13 pts), boolean chains 11, ternaries 3 (nesting depth added 1). Most of this is not in the body itself: 1 of the 27 points is its own statement and the rest belongs to 9 function items inside it that branch (a function literal at line 52, a function literal at line 70, a function literal at line 151, …). 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.
DocumentMapper.fromConversationIndex (cognitive 26) backend/components/communication/src/main/java/co/airy/core/communication/lucene/DocumentMapper.java:25— DocumentMapper.fromConversationIndex has cognitive complexity 26 (threshold 15). Drivers by points: if/else 20 (22 pts), loops 2 (4 pts) (nesting depth added 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.
index.CatalogCard (cognitive 26) frontend/control-center/src/pages/Catalog/CatalogCard/index.tsx:49— index.CatalogCard has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 13, ternaries 5 (8 pts), if/else 5 (nesting depth added 3). Most of this is not in the body itself: 10 of the 26 points are its own statements and the rest belongs to 5 function items inside it that branch (CatalogCardButton, a function literal at line 79, handleCardClick, …). 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.
FacebookConnect.FacebookConnect (cognitive 26) frontend/control-center/src/pages/Connectors/Providers/Facebook/Messenger/FacebookConnect.tsx:23— FacebookConnect.FacebookConnect has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 17, ternaries 6 (7 pts), if/else 2 (nesting depth added 1). Of this number, 14 points are the body's own statements and 12 belong to 5 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.
index.AiryInputBar (cognitive 25) frontend/chat-plugin/lib/src/airyRenderProps/AiryInputBar/index.tsx:26— index.AiryInputBar has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 13, if/else 11 (12 pts) (nesting depth added 1). Most of this is not in the body itself: 4 of the 25 points are its own statements and the rest belongs to 13 function items inside it that branch (handleKeyDown, AttachmentInput::acceptedFileTypes, onSubmit, …). 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.
index.ConnectorWrapper (cognitive 25) frontend/control-center/src/pages/Connectors/ConnectorWrapper/index.tsx:38— index.ConnectorWrapper has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 16, if/else 6 (7 pts), ternaries 2 (nesting depth added 1). Most of this is not in the body itself: 10 of the 25 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 80, determineBackRoute, a function literal at line 88, …). 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.
GoogleConnect.GoogleConnect (cognitive 25) frontend/control-center/src/pages/Connectors/Providers/Google/GoogleConnect.tsx:27— GoogleConnect.GoogleConnect has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 15, ternaries 6 (7 pts), if/else 3 (nesting depth added 1). Of this number, 13 points are the body's own statements and 12 belong to 6 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
index.CatalogItemDetails::SideColumnContent (cognitive 25) frontend/control-center/src/pages/Catalog/CatalogItemDetails/index.tsx:184— index.CatalogItemDetails::SideColumnContent has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 9 (20 pts), boolean chains 5 (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.
index.NotificationComponent (cognitive 25) lib/typescript/components/alerts/NotificationComponent/index.tsx:23— index.NotificationComponent has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 12, if/else 6 (8 pts), ternaries 4 (5 pts) (nesting depth added 3). Most of this is not in the body itself: 12 of the 25 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 39, 56, 35). 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.
WhatsappConnect.WhatsappConnect (cognitive 24) frontend/control-center/src/pages/Connectors/Providers/WhatsappBusinessCloud/WhatsappConnect.tsx:23— WhatsappConnect.WhatsappConnect has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 16, ternaries 5 (6 pts), if/else 2 (nesting depth added 1). Of this number, 14 points are the body's own statements and 10 belong to 5 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.
index.Creation (cognitive 24) frontend/control-center/src/pages/Streams/Creation/index.tsx:31— index.Creation has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 11, if/else 8 (9 pts), ternaries 4 (nesting depth added 1). Of this number, 12 points are the body's own statements and 12 belong to 11 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.
TopicsFinder.processFile (cognitive 22) infrastructure/tools/topics/src/main/java/co/airy/tools/topics/TopicsFinder.java:54— TopicsFinder.processFile has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (8 pts), ternaries 2 (7 pts), loops 2 (4 pts), error handling 1 (2 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.
Helm.runHelm (cognitive 22) cli/pkg/helm/helm.go:99— Helm.runHelm has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 3 (9 pts), match/switch 1 (2 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.
handler.getContainerWithEnvReference (cognitive 21) infrastructure/lib/go/k8s/handler/containers.go:52— handler.getContainerWithEnvReference has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 3 (5 pts), boolean chains 4 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
index.ConnectorConfig (cognitive 21) frontend/control-center/src/pages/Connectors/ConnectorConfig/index.tsx:38— index.ConnectorConfig has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 26, if/else 16 (24 pts), ternaries 1 (nesting depth added 8). 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. This shape REPEATS in the file: one other method here (index.ConnectorConfig::PageContent) 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.
Popup.PopUpFilter (cognitive 21) frontend/inbox/src/pages/Inbox/QuickFilter/Popup.tsx:46— Popup.PopUpFilter has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 10, ternaries 7, if/else 4. Most of this is not in the body itself: 10 of the 21 points are its own statements and the rest belongs to 9 function items inside it that branch (toggleTag, a function literal at line 97, setState, …). 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.
index.Carousel (cognitive 21) lib/typescript/components/general/Carousel/index.tsx:7— index.Carousel has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 6, loops 2 (nesting depth added 3). None of this is in the body itself: all 21 points belong to 5 function items inside it that branch (a function literal at line 88, maximumScrollRight, maximumScrollLeft, …). 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.
TopicDescription.TopicDescription (cognitive 20) frontend/control-center/src/pages/Topics/TopicItem/TopicDescription/TopicDescription.tsx:14— TopicDescription.TopicDescription has cognitive complexity 20 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 3, ternaries 3 (nesting depth added 2). Most of this is not in the body itself: 4 of the 20 points are its own statements and the rest belongs to 5 function items inside it that branch (recalculateContainerHeight, calculateRetentionTime, calculateRetentionSize, …). 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.
handler.GetDeploymentsReferencingCm (cognitive 19) infrastructure/lib/go/k8s/handler/deployments.go:17— handler.GetDeploymentsReferencingCm has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 1, loops 1 (nesting depth added 9). None of this is in the body itself: all 19 points belong to one function literal inside it that branches (line 20). 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.
ChatPluginConnect.ChatPluginConnect (cognitive 19) frontend/control-center/src/pages/Connectors/Providers/Airy/ChatPlugin/ChatPluginConnect.tsx:46— ChatPluginConnect.ChatPluginConnect has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 7, ternaries 6, if/else 3 (5 pts), match/switch 1 (nesting depth added 2). Of this number, 11 points are the body's own statements and 8 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.
InstagramConnect.InstagramConnect (cognitive 19) frontend/control-center/src/pages/Connectors/Providers/Instagram/InstagramConnect.tsx:17— InstagramConnect.InstagramConnect has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 15, if/else 2, ternaries 2. Of this number, 10 points are the body's own statements and 9 belong to 3 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.
index.ConnectorConfig::PageContent (cognitive 19) frontend/control-center/src/pages/Connectors/ConnectorConfig/index.tsx:115— index.ConnectorConfig::PageContent has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (18 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. This shape REPEATS in the file: one other method here (index.ConnectorConfig) 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.
index.MessengerContainer (cognitive 19) frontend/inbox/src/pages/Inbox/Messenger/MessengerContainer/index.tsx:30— index.MessengerContainer has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (11 pts), boolean chains 7, ternaries 1 (nesting depth added 1). Most of this is not in the body itself: 4 of the 19 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 42, a function literal at line 100, handleDragLeave, …). 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.
main.sendFlinkSQL (cognitive 18) REDACTED:18— main.sendFlinkSQL has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (14 pts), loops 3 (4 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
index.TopBar (cognitive 18) frontend/control-center/src/components/TopBar/index.tsx:37— index.TopBar has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 11, ternaries 4, if/else 2, match/switch 1. Of this number, 15 points are the body's own statements and 3 belong to 2 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.
InstallSection.InstallSection::getTemplateConfig (cognitive 18) frontend/control-center/src/pages/Connectors/Providers/Airy/ChatPlugin/sections/InstallSection/InstallSection.tsx:49— InstallSection.InstallSection::getTemplateConfig has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 15, ternaries 3. 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.
index.ConversationMetadata (cognitive 18) frontend/inbox/src/pages/Inbox/Messenger/ConversationMetadata/index.tsx:55— index.ConversationMetadata has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 9, if/else 6 (7 pts), ternaries 2 (nesting depth added 1). Most of this is not in the body itself: 5 of the 18 points are its own statements and the rest belongs to 7 function items inside it that branch (submitForm, renderTagsDialog, checkIfExists, …). 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.
index.AudioRecording (cognitive 18) frontend/inbox/src/pages/Inbox/MessageInput/AudioRecording/index.tsx:34— index.AudioRecording has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 7, error handling 1, ternaries 1 (nesting depth added 1). Most of this is not in the body itself: 5 of the 18 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 107, 76, 131, …). 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.
InputComponent.render (cognitive 18) lib/typescript/components/inputs/Input/index.tsx:260— InputComponent.render has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 9, ternaries 6 (9 pts) (nesting depth added 3). 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.
Stores.onApplicationEvent (cognitive 17) backend/components/contacts/src/main/java/co/airy/core/contacts/Stores.java:66— Stores.onApplicationEvent has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 5 (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.
Contact.toMetadata (cognitive 17) backend/model/contact/src/main/java/co/airy/model/contact/Contact.java:216— Contact.toMetadata has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12, boolean chains 3, error handling 1 (2 pts) (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.
StreamsCreate.ServeHTTP (cognitive 17) backend/components/streams/streams_create.go:29— StreamsCreate.ServeHTTP has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (14 pts), loops 2 (3 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ViberConnect.ViberConnect (cognitive 17) frontend/control-center/src/pages/Connectors/Providers/Viber/ViberConnect.tsx:23— ViberConnect.ViberConnect has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 13, ternaries 4. Of this number, 10 points are the body's own statements and 7 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.
index.TopBar (cognitive 17) frontend/inbox/src/components/TopBar/index.tsx:38— index.TopBar has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 9, ternaries 5, if/else 2, match/switch 1. 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, 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.
TableRow.TableRowComponent (cognitive 17) frontend/inbox/src/pages/Tags/TableRow.tsx:25— TableRow.TableRowComponent has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 12, if/else 5. 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 44, 78, 99). 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.
index.Suggestions (cognitive 17) lib/typescript/render/providers/google/components/Suggestions/index.tsx:23— index.Suggestions has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 7, ternaries 3 (6 pts), if/else 4 (nesting depth added 3). Most of this is not in the body itself: 6 of the 17 points are its own statements and the rest belongs to one function literal inside it that branches (line 30). 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.
GoogleRender.googleInbound (cognitive 17) lib/typescript/render/providers/google/GoogleRender.tsx:60— GoogleRender.googleInbound has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 5 (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.
MessageMapper.getRecords (cognitive 16) backend/components/facebook/events-router/src/main/java/co/airy/core/sources/facebook/MessageMapper.java:57— MessageMapper.getRecords has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 5, ternaries 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.
InputSelector.InputSelector (cognitive 16) frontend/inbox/src/pages/Inbox/MessageInput/InputSelector.tsx:18— InputSelector.InputSelector has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 3, loops 1 (nesting depth added 5). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 2 function items inside it that branch (scaleDownInputSelector, a function literal at line 29). 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.
GoogleRender.googleOutbound (cognitive 16) lib/typescript/render/providers/google/GoogleRender.tsx:152— GoogleRender.googleOutbound has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 2 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D22 · Internal API Consistency· `k8s.ApplyConfigMap` takes its context.Context last where 2 members of the package take it first · ×1
`k8s.ApplyConfigMap` takes its context.Context last where 2 members of the package take it first lib/go/k8s/configmaps.go:13— 2 of 3 members of package k8s with a context take it as the first parameter, the context package's own rule (2 of 3). Siblings: k8s.GetInstalledComponents (lib/go/k8s/configmaps.go:76); k8s.GetComponentsConfigMaps (lib/go/k8s/configmaps.go:88). Move `ctx context.Context` to the front of the parameter list. [rule A2]
MethodTooLong: InputComponent.render lib/typescript/components/inputs/Input/index.tsx:260— MethodTooLong — render runs 140 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 40 over it, 1.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.
D30 · Dependency Vulnerabilities· Medium vulnerability · ×1
Change coupling: Components.ts ↔ translations.ts lib/typescript/model/Components.ts:1— `lib/typescript/model/Components.ts` and `lib/typescript/translations/translations.ts` 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 `b38e5b2e` [#3841] Add translations catalog components (#3972); `ef9c6992` [#3669] remove component naming types in the control center (#3676); `08337ff1` [#3491] Added Whatsapp Business Cloud (#3647) — run `git show` on any of them.
Near-duplicate member pair (27 shared lines) backend/components/facebook/events-router/src/main/java/co/airy/core/sources/facebook/EventsRouter.java:63— backend/components/facebook/events-router/src/main/java/co/airy/core/sources/facebook/EventsRouter.java:63-136 | backend/components/whatsapp/events-router/src/main/java/co/airy/core/sources/whatsapp/EventsRouter.java:61-130 — These two members are variants of one another: 27 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (6 members, 50+ identical tokens) backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/Connector.java:56— backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/Connector.java:56-99 | backend/components/google/connector/src/main/java/co/airy/core/sources/google/Connector.java:45-80 | backend/components/sources-api/src/main/java/co/airy/core/sources/api/actions/Actions.java:27-41 | backend/components/twilio/connector/src/main/java/co/airy/core/sources/twilio/Connector.java:43-81 | backend/components/viber/connector/src/main/java/co/airy/core/sources/viber/Connector.java:45-67 | backend/components/whatsapp/connector/src/main/java/co/airy/core/sources/whatsapp/Connector.java:46-85 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (4 members, 50+ identical tokens) backend/components/cognigy/src/main/java/co/airy/core/cognigy_connector/Stores.java:36— backend/components/cognigy/src/main/java/co/airy/core/cognigy_connector/Stores.java:36-60 | backend/components/google/events-router/src/main/java/co/airy/core/sources/google/EventsRouter.java:72-175 | backend/components/ibm-watson-assistant/src/main/java/co/airy/core/ibm_watson_assistant_connector/Stores.java:36-60 | backend/components/rasa/src/main/java/co/airy/core/rasa_connector/Stores.java:34-57 — 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 (127 corresponding lines) · ×1
Edited copy of a member (127 corresponding lines) REDACTED:15— REDACTED:15-158 | REDACTED:14-140 — These two members are one piece of code written twice and then edited apart: 127 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 (52 corresponding lines) · ×1
Edited copy of a member (52 corresponding lines) backend/components/twilio/connector/src/main/java/co/airy/core/sources/twilio/Stores.java:54— backend/components/twilio/connector/src/main/java/co/airy/core/sources/twilio/Stores.java:54-105 | backend/components/viber/connector/src/main/java/co/airy/core/sources/viber/Stores.java:56-111 — These two members are one piece of code written twice and then edited apart: 52 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (37 corresponding lines) · ×1
Edited copy of a member (37 corresponding lines) backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/ChannelsController.java:85— backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/ChannelsController.java:85-122 | backend/components/whatsapp/connector/src/main/java/co/airy/core/sources/whatsapp/ChannelsController.java:39-75 — These two members are one piece of code written twice and then edited apart: 37 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 27+ corresponding lines) · ×1
Edited copies of one member (3 members, 27+ corresponding lines) backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/api/Api.java:175— backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/api/Api.java:175-201 | backend/components/google/connector/src/main/java/co/airy/core/sources/google/services/Api.java:60-86 | backend/components/whatsapp/connector/src/main/java/co/airy/core/sources/whatsapp/api/Api.java:92-118 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 27 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, 32+ corresponding lines) · ×1
Edited copies of one member (3 members, 32+ corresponding lines) backend/components/admin/src/main/java/co/airy/core/admin/ChannelsController.java:89— backend/components/admin/src/main/java/co/airy/core/admin/ChannelsController.java:89-120 | backend/components/google/connector/src/main/java/co/airy/core/sources/google/ChannelsController.java:39-70 | backend/components/sources-api/src/main/java/co/airy/core/sources/api/ChannelsController.java:45-76 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 32 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, 24+ corresponding lines) · ×1
Edited copies of one member (4 members, 24+ corresponding lines) backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/ChannelsController.java:174— backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/ChannelsController.java:174-197 | backend/components/google/connector/src/main/java/co/airy/core/sources/google/ChannelsController.java:73-96 | backend/components/twilio/connector/src/main/java/co/airy/core/sources/twilio/ChannelsController.java:96-119 | backend/components/whatsapp/connector/src/main/java/co/airy/core/sources/whatsapp/ChannelsController.java:78-101 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 24 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 (15 corresponding lines) · ×1
Edited copy of a member (15 corresponding lines) backend/components/cognigy/src/main/java/co/airy/core/cognigy_connector/CognigyConnectorService.java:38— backend/components/cognigy/src/main/java/co/airy/core/cognigy_connector/CognigyConnectorService.java:38-52 | backend/components/rasa/src/main/java/co/airy/core/rasa_connector/RasaConnectorService.java:33-52 — 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 (19 corresponding lines) · ×1
Edited copy of a member (19 corresponding lines) backend/components/admin/src/main/java/co/airy/core/admin/WebhooksController.java:123— backend/components/admin/src/main/java/co/airy/core/admin/WebhooksController.java:123-141 | backend/components/communication/src/main/java/co/airy/core/communication/SendMessageController.java:113-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 copies of one member (6 members, 18+ corresponding lines) · ×1
Edited copies of one member (6 members, 18+ corresponding lines) backend/components/communication/src/main/java/co/airy/core/communication/ConversationsController.java:146— backend/components/communication/src/main/java/co/airy/core/communication/ConversationsController.java:146-165 | backend/components/communication/src/main/java/co/airy/core/communication/ConversationsController.java:168-187 | backend/components/communication/src/main/java/co/airy/core/communication/ConversationsController.java:190-209 | backend/components/communication/src/main/java/co/airy/core/communication/ConversationsController.java:212-229 | backend/components/communication/src/main/java/co/airy/core/communication/ConversationsController.java:232-251 | backend/components/communication/src/main/java/co/airy/core/communication/ConversationsController.java:254-274 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 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) backend/components/chat-plugin/src/main/java/co/airy/core/chat_plugin/config/Jwt.java:76— backend/components/chat-plugin/src/main/java/co/airy/core/chat_plugin/config/Jwt.java:76-96 | backend/components/chat-plugin/src/main/java/co/airy/core/chat_plugin/config/Jwt.java:98-118 — 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, 18+ corresponding lines) · ×1
Edited copies of one member (3 members, 18+ corresponding lines) backend/components/chat-plugin/src/main/java/co/airy/core/chat_plugin/config/Jwt.java:38— backend/components/chat-plugin/src/main/java/co/airy/core/chat_plugin/config/Jwt.java:38-55 | backend/components/chat-plugin/src/main/java/co/airy/core/chat_plugin/config/Jwt.java:57-74 | lib/java/spring/auth/src/main/java/co/airy/spring/auth/Jwt.java:35-52 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 20+ corresponding lines) · ×1
Edited copies of one member (3 members, 20+ corresponding lines) cli/pkg/providers/aws/aws.go:64— cli/pkg/providers/aws/aws.go:64-83 | cli/pkg/providers/gcp/gcp.go:64-83 | cli/pkg/providers/minikube/minikube.go:68-87 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 19+ corresponding lines) · ×1
Edited copies of one member (3 members, 19+ corresponding lines) cli/pkg/providers/aws/aws.go:38— cli/pkg/providers/aws/aws.go:38-56 | cli/pkg/providers/gcp/gcp.go:38-56 | cli/pkg/providers/minikube/minikube.go:48-66 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 14+ corresponding lines) · ×1
Edited copies of one member (3 members, 14+ corresponding lines) backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/WebhookController.java:61— backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/WebhookController.java:61-74 | backend/components/google/connector/src/main/java/co/airy/core/sources/google/WebhookController.java:58-71 | backend/components/whatsapp/connector/src/main/java/co/airy/core/sources/whatsapp/WebhookController.java:65-80 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 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, 11+ corresponding lines) · ×1
Edited copies of one member (3 members, 11+ corresponding lines) backend/components/installer/src/main/java/co/airy/core/api/components/installer/InstallerController.java:35— backend/components/installer/src/main/java/co/airy/core/api/components/installer/InstallerController.java:35-46 | backend/components/installer/src/main/java/co/airy/core/api/components/installer/InstallerController.java:49-59 | backend/components/installer/src/main/java/co/airy/core/api/components/installer/InstallerController.java:62-72 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (20 corresponding lines) · ×1
Edited copy of a member (20 corresponding lines) backend/components/admin/src/main/java/co/airy/core/admin/TimestampExtractor.java:14— backend/components/admin/src/main/java/co/airy/core/admin/TimestampExtractor.java:14-33 | backend/components/twilio/events-router/src/main/java/co/airy/core/sources/twilio/TimestampExtractor.java:16-38 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×1
Edited copy of a member (10 corresponding lines) backend/components/sources-api/src/main/java/co/airy/core/sources/api/services/SourceToken.java:41— backend/components/sources-api/src/main/java/co/airy/core/sources/api/services/SourceToken.java:41-50 | backend/components/sources-api/src/main/java/co/airy/core/sources/api/services/SourceToken.java:61-72 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×1
Edited copy of a member (9 corresponding lines) backend/components/webhook/consumer/src/main/java/co/airy/core/webhook/consumer/config/BeanstalkConsumerConfig.java:13— backend/components/webhook/consumer/src/main/java/co/airy/core/webhook/consumer/config/BeanstalkConsumerConfig.java:13-21 | backend/components/webhook/publisher/src/main/java/co/airy/core/webhook/publisher/config/BeanstalkProducerConfig.java:13-21 — 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.
Duplicated block (16–19 lines × 2) backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/Stores.java:94— backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/Stores.java:94-109 | backend/components/whatsapp/connector/src/main/java/co/airy/core/sources/whatsapp/Stores.java:96-114 — before extracting anything, compare `backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/Stores.java` and `backend/components/whatsapp/connector/src/main/java/co/airy/core/sources/whatsapp/Stores.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 37 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 `backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/Stores.java: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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. Note first that the copies are not typed on the same thing: `Conversation` names `co.airy.core.sources.facebook.dto.Conversation` in one and `co.airy.core.sources.whatsapp.dto.Conversation` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (18 lines × 3) backend/components/cognigy/src/main/java/co/airy/core/cognigy_connector/MessageHandler.java:24— backend/components/cognigy/src/main/java/co/airy/core/cognigy_connector/MessageHandler.java:24-41 | backend/components/ibm-watson-assistant/src/main/java/co/airy/core/ibm_watson_assistant_connector/MessageHandler.java:27-44 | backend/components/rasa/src/main/java/co/airy/core/rasa_connector/MessageHandler.java:25-42 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: `MessageSendResponse` names `co.airy.core.cognigy.models.MessageSendResponse` in one and `co.airy.core.ibm_watson_assistant.models.MessageSendResponse` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (17 lines × 3) backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/api/Api.java:185— backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/api/Api.java:185-201 | backend/components/google/connector/src/main/java/co/airy/core/sources/google/services/Api.java:70-86 | backend/components/whatsapp/connector/src/main/java/co/airy/core/sources/whatsapp/api/Api.java:102-118 — before extracting anything, compare `backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/api/Api.java` and `backend/components/google/connector/src/main/java/co/airy/core/sources/google/services/Api.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 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 `backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/api/Api.java:185` 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–16 lines × 5) backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/ChannelsController.java:175— backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/ChannelsController.java:175-190 | backend/components/google/connector/src/main/java/co/airy/core/sources/google/ChannelsController.java:74-89 | backend/components/twilio/connector/src/main/java/co/airy/core/sources/twilio/ChannelsController.java:97-112 | backend/components/viber/connector/src/main/java/co/airy/core/sources/viber/ChannelsController.java:97-111 | backend/components/whatsapp/connector/src/main/java/co/airy/core/sources/whatsapp/ChannelsController.java:79-94 — before extracting anything, compare `backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/ChannelsController.java` and `backend/components/whatsapp/connector/src/main/java/co/airy/core/sources/whatsapp/ChannelsController.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 51 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 `backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/ChannelsController.java:175` 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 first that the copies are not typed on the same thing: `Api` names `co.airy.core.sources.viber.services.Api` in one and `co.airy.core.sources.whatsapp.api.Api` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `backend/components/viber/connector/src/main/java/co/airy/core/sources/viber/ChannelsController.java:112` calls `removeWebhook` and `backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/ChannelsController.java: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 (17 lines × 2) backend/components/admin/src/main/java/co/airy/core/admin/ChannelsController.java:95— backend/components/admin/src/main/java/co/airy/core/admin/ChannelsController.java:95-111 | backend/components/google/connector/src/main/java/co/airy/core/sources/google/ChannelsController.java:46-62 — 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 (15 lines × 6) backend/components/admin/src/main/java/co/airy/core/admin/ChannelsController.java:133— backend/components/admin/src/main/java/co/airy/core/admin/ChannelsController.java:133-147 | backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/ChannelsController.java:183-197 | backend/components/google/connector/src/main/java/co/airy/core/sources/google/ChannelsController.java:82-96 | backend/components/sources-api/src/main/java/co/airy/core/sources/api/ChannelsController.java:102-116 | backend/components/twilio/connector/src/main/java/co/airy/core/sources/twilio/ChannelsController.java:105-119 | backend/components/whatsapp/connector/src/main/java/co/airy/core/sources/whatsapp/ChannelsController.java:87-101 — before extracting anything, compare `backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/ChannelsController.java` and `backend/components/whatsapp/connector/src/main/java/co/airy/core/sources/whatsapp/ChannelsController.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 51 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 `backend/components/admin/src/main/java/co/airy/core/admin/ChannelsController.java:133` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `backend/components/admin/src/main/java/co/airy/core/admin/ChannelsController.java:132` calls `getChannel` and `backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/ChannelsController.java:181` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (15 lines × 2) backend/components/twilio/connector/src/main/java/co/airy/core/sources/twilio/WebhookController.java:91— backend/components/twilio/connector/src/main/java/co/airy/core/sources/twilio/WebhookController.java:91-105 | lib/java/url/src/main/java/co/airy/url/UrlUtil.java:13-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. 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–14 lines × 6) backend/components/google/connector/src/main/java/co/airy/core/sources/google/Stores.java:74— backend/components/google/connector/src/main/java/co/airy/core/sources/google/Stores.java:74-86 | backend/components/sources-api/src/main/java/co/airy/core/sources/api/Stores.java:124-137 | backend/components/twilio/connector/src/main/java/co/airy/core/sources/twilio/Stores.java:93-105 | backend/components/viber/connector/src/main/java/co/airy/core/sources/viber/Stores.java:98-111 | backend/components/whatsapp/connector/src/main/java/co/airy/core/sources/whatsapp/Stores.java:119-131 | backend/components/whatsapp/events-router/src/main/java/co/airy/core/sources/whatsapp/EventsRouter.java:117-130 — before extracting anything, compare `backend/components/google/connector/src/main/java/co/airy/core/sources/google/Stores.java` and `backend/components/twilio/connector/src/main/java/co/airy/core/sources/twilio/Stores.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 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 `backend/components/google/connector/src/main/java/co/airy/core/sources/google/Stores.java:74` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 4) backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/api/Api.java:176— backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/api/Api.java:176-189 | backend/components/google/connector/src/main/java/co/airy/core/sources/google/services/Api.java:61-74 | backend/components/viber/connector/src/main/java/co/airy/core/sources/viber/services/Api.java:99-112 | backend/components/whatsapp/connector/src/main/java/co/airy/core/sources/whatsapp/api/Api.java:93-106 — before extracting anything, compare `backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/api/Api.java` and `backend/components/google/connector/src/main/java/co/airy/core/sources/google/services/Api.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 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 `backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/api/Api.java:176` 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, `backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/api/Api.java:190` calls `get` and `backend/components/viber/connector/src/main/java/co/airy/core/sources/viber/services/Api.java:113` 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 × 3) backend/components/cognigy/src/main/java/co/airy/core/cognigy_connector/CognigyConnectorService.java:55— backend/components/cognigy/src/main/java/co/airy/core/cognigy_connector/CognigyConnectorService.java:55-68 | backend/components/ibm-watson-assistant/src/main/java/co/airy/core/ibm_watson_assistant_connector/IbmWatsonAssistantConnectorService.java:61-74 | backend/components/rasa/src/main/java/co/airy/core/rasa_connector/RasaConnectorService.java:55-68 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (14 lines × 2) backend/components/contacts/src/main/java/co/airy/core/contacts/payload/ContactResponsePayload.java:35— backend/components/contacts/src/main/java/co/airy/core/contacts/payload/ContactResponsePayload.java:35-48 | backend/components/contacts/src/main/java/co/airy/core/contacts/payload/ContactWithMergeHistoryResponsePayload.java:41-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 `backend/components/contacts/src/main/java/co/airy/core/contacts/payload/ContactResponsePayload.java:35` 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 × 4) backend/components/cognigy/src/main/java/co/airy/core/cognigy_connector/Stores.java:48— backend/components/cognigy/src/main/java/co/airy/core/cognigy_connector/Stores.java:48-60 | backend/components/google/events-router/src/main/java/co/airy/core/sources/google/EventsRouter.java:163-175 | backend/components/ibm-watson-assistant/src/main/java/co/airy/core/ibm_watson_assistant_connector/Stores.java:48-60 | backend/components/rasa/src/main/java/co/airy/core/rasa_connector/Stores.java:45-57 — before extracting anything, compare `backend/components/cognigy/src/main/java/co/airy/core/cognigy_connector/Stores.java` and `backend/components/rasa/src/main/java/co/airy/core/rasa_connector/Stores.java` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `backend/components/cognigy/src/main/java/co/airy/core/cognigy_connector/Stores.java:48` 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) backend/components/communication/src/main/java/co/airy/core/communication/Stores.java:126— backend/components/communication/src/main/java/co/airy/core/communication/Stores.java:126-138 | backend/components/webhook/publisher/src/main/java/co/airy/core/webhook/publisher/Stores.java:91-103 — 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 `backend/components/communication/src/main/java/co/airy/core/communication/Stores.java:126` 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, `backend/components/communication/src/main/java/co/airy/core/communication/Stores.java:140` calls `getMessage`, `getIsFromContact`, `setSourceConversationId` and `backend/components/webhook/publisher/src/main/java/co/airy/core/webhook/publisher/Stores.java:105` 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–12 lines × 2) backend/components/twilio/connector/src/main/java/co/airy/core/sources/twilio/Stores.java:67— backend/components/twilio/connector/src/main/java/co/airy/core/sources/twilio/Stores.java:67-78 | backend/components/viber/connector/src/main/java/co/airy/core/sources/viber/Stores.java:64-74 — before extracting anything, compare `backend/components/twilio/connector/src/main/java/co/airy/core/sources/twilio/Stores.java` and `backend/components/viber/connector/src/main/java/co/airy/core/sources/viber/Stores.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 33 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 `backend/components/twilio/connector/src/main/java/co/airy/core/sources/twilio/Stores.java:67` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: `SendMessageRequest` names `co.airy.core.sources.twilio.dto.SendMessageRequest` in one and `co.airy.core.sources.viber.dto.SendMessageRequest` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `backend/components/viber/connector/src/main/java/co/airy/core/sources/viber/Stores.java:76` calls `channelId`, `getChannelId` and `backend/components/twilio/connector/src/main/java/co/airy/core/sources/twilio/Stores.java:80` 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 lines × 4) backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/Stores.java:114— backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/Stores.java:114-124 | backend/components/google/connector/src/main/java/co/airy/core/sources/google/Stores.java:73-83 | backend/components/viber/connector/src/main/java/co/airy/core/sources/viber/Stores.java:83-93 | backend/components/whatsapp/connector/src/main/java/co/airy/core/sources/whatsapp/Stores.java:118-128 — before extracting anything, compare `backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/Stores.java` and `backend/components/whatsapp/connector/src/main/java/co/airy/core/sources/whatsapp/Stores.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 37 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 `backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/Stores.java:114` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/ChannelsController.java:97— backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/ChannelsController.java:97-107 | backend/components/whatsapp/connector/src/main/java/co/airy/core/sources/whatsapp/ChannelsController.java:48-58 — before extracting anything, compare `backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/ChannelsController.java` and `backend/components/whatsapp/connector/src/main/java/co/airy/core/sources/whatsapp/ChannelsController.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 51 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 `backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/ChannelsController.java:97` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: `Api` names `co.airy.core.sources.facebook.api.Api` in one and `co.airy.core.sources.whatsapp.api.Api` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/ChannelsController.java:93` calls `getPageForUser`, `connectPageToApp`, `getAccessToken` and `backend/components/whatsapp/connector/src/main/java/co/airy/core/sources/whatsapp/ChannelsController.java:46` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9–10 lines × 2) backend/components/admin/src/main/java/co/airy/core/admin/WebhooksController.java:41— backend/components/admin/src/main/java/co/airy/core/admin/WebhooksController.java:41-49 | backend/components/admin/src/main/java/co/airy/core/admin/WebhooksController.java:73-82 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) REDACTED:50— REDACTED:50-59 | REDACTED:119-128 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 5) backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/api/Api.java:177— backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/api/Api.java:177-185 | backend/components/google/connector/src/main/java/co/airy/core/sources/google/services/Api.java:62-70 | backend/components/sources-api/src/main/java/co/airy/core/sources/api/actions/EndpointConfig.java:21-29 | backend/components/viber/connector/src/main/java/co/airy/core/sources/viber/services/Api.java:100-108 | backend/components/whatsapp/connector/src/main/java/co/airy/core/sources/whatsapp/api/Api.java:94-102 — before extracting anything, compare `backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/api/Api.java` and `backend/components/google/connector/src/main/java/co/airy/core/sources/google/services/Api.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 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 `backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/api/Api.java:177` 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 × 3) backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/ChannelsController.java:114— backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/ChannelsController.java:114-122 | backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/ChannelsController.java:163-171 | backend/components/whatsapp/connector/src/main/java/co/airy/core/sources/whatsapp/ChannelsController.java:67-75 — before extracting anything, compare `backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/ChannelsController.java` and `backend/components/whatsapp/connector/src/main/java/co/airy/core/sources/whatsapp/ChannelsController.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 51 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 `backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/ChannelsController.java:114` 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. Note first that the copies are not typed on the same thing: `Api` names `co.airy.core.sources.facebook.api.Api` in one and `co.airy.core.sources.whatsapp.api.Api` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (7–9 lines × 2) backend/components/google/connector/src/main/java/co/airy/core/sources/google/Stores.java:65— backend/components/google/connector/src/main/java/co/airy/core/sources/google/Stores.java:65-71 | backend/components/twilio/connector/src/main/java/co/airy/core/sources/twilio/Stores.java:75-83 — before extracting anything, compare `backend/components/google/connector/src/main/java/co/airy/core/sources/google/Stores.java` and `backend/components/twilio/connector/src/main/java/co/airy/core/sources/twilio/Stores.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 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 `backend/components/google/connector/src/main/java/co/airy/core/sources/google/Stores.java:65` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (8 lines × 3) backend/components/cognigy/src/main/java/co/airy/core/cognigy_connector/Stores.java:38— backend/components/cognigy/src/main/java/co/airy/core/cognigy_connector/Stores.java:38-45 | backend/components/ibm-watson-assistant/src/main/java/co/airy/core/ibm_watson_assistant_connector/Stores.java:38-45 | backend/components/rasa/src/main/java/co/airy/core/rasa_connector/Stores.java:35-42 — before extracting anything, compare `backend/components/cognigy/src/main/java/co/airy/core/cognigy_connector/Stores.java` and `backend/components/rasa/src/main/java/co/airy/core/rasa_connector/Stores.java` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `backend/components/cognigy/src/main/java/co/airy/core/cognigy_connector/Stores.java:38` 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.
Duplicated block (7–8 lines × 2) backend/components/cognigy/src/main/java/co/airy/core/cognigy_connector/CognigyConnectorService.java:46— backend/components/cognigy/src/main/java/co/airy/core/cognigy_connector/CognigyConnectorService.java:46-52 | backend/components/ibm-watson-assistant/src/main/java/co/airy/core/ibm_watson_assistant_connector/IbmWatsonAssistantConnectorService.java:51-58 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `backend/components/cognigy/src/main/java/co/airy/core/cognigy_connector/CognigyConnectorService.java:46` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (7 lines × 5) backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/Stores.java:145— backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/Stores.java:145-151 | backend/components/google/connector/src/main/java/co/airy/core/sources/google/Stores.java:94-100 | backend/components/twilio/connector/src/main/java/co/airy/core/sources/twilio/Stores.java:112-118 | backend/components/viber/connector/src/main/java/co/airy/core/sources/viber/Stores.java:118-124 | backend/components/whatsapp/connector/src/main/java/co/airy/core/sources/whatsapp/Stores.java:138-144 — before extracting anything, compare `backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/Stores.java` and `backend/components/whatsapp/connector/src/main/java/co/airy/core/sources/whatsapp/Stores.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (7 lines × 3) backend/components/installer/src/main/java/co/airy/core/api/components/installer/InstallerController.java:39— backend/components/installer/src/main/java/co/airy/core/api/components/installer/InstallerController.java:39-46 | backend/components/installer/src/main/java/co/airy/core/api/components/installer/InstallerController.java:53-59 | backend/components/installer/src/main/java/co/airy/core/api/components/installer/InstallerController.java:66-72 — 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 `backend/components/installer/src/main/java/co/airy/core/api/components/installer/InstallerController.java:39` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (3–7 lines × 3) backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/Connector.java:88— backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/Connector.java:88-94 | backend/components/twilio/connector/src/main/java/co/airy/core/sources/twilio/Connector.java:69-71 | backend/components/whatsapp/connector/src/main/java/co/airy/core/sources/whatsapp/Connector.java:74-80 — before extracting anything, compare `backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/Connector.java` and `backend/components/whatsapp/connector/src/main/java/co/airy/core/sources/whatsapp/Connector.java` 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. 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 `backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/Connector.java:88` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. Note first that the copies are not typed on the same thing: `SendMessageRequest` names `co.airy.core.sources.facebook.dto.SendMessageRequest` in one and `co.airy.core.sources.twilio.dto.SendMessageRequest` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/Connector.java:87` calls `newMessageMetadata`, `getId`, `getErrorPayload` and `backend/components/twilio/connector/src/main/java/co/airy/core/sources/twilio/Connector.java:69` 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) backend/components/communication/src/main/java/co/airy/core/communication/ConversationsController.java:193— backend/components/communication/src/main/java/co/airy/core/communication/ConversationsController.java:193-198 | backend/components/communication/src/main/java/co/airy/core/communication/ConversationsController.java:235-240 | backend/components/communication/src/main/java/co/airy/core/communication/ConversationsController.java:256-261 — 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 (5 lines × 5) backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/WebhookController.java:43— backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/WebhookController.java:43-48 | backend/components/google/connector/src/main/java/co/airy/core/sources/google/WebhookController.java:43-48 | backend/components/twilio/connector/src/main/java/co/airy/core/sources/twilio/WebhookController.java:46-50 | backend/components/viber/connector/src/main/java/co/airy/core/sources/viber/WebhookController.java:44-48 | backend/components/whatsapp/connector/src/main/java/co/airy/core/sources/whatsapp/WebhookController.java:47-52 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/WebhookController.java:43` 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 (2–5 lines × 6) backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/Connector.java:92— backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/Connector.java:92-96 | backend/components/google/connector/src/main/java/co/airy/core/sources/google/Connector.java:76-77 | backend/components/sources-api/src/main/java/co/airy/core/sources/api/actions/Actions.java:37-38 | backend/components/twilio/connector/src/main/java/co/airy/core/sources/twilio/Connector.java:74-78 | backend/components/viber/connector/src/main/java/co/airy/core/sources/viber/Connector.java:63-64 | backend/components/whatsapp/connector/src/main/java/co/airy/core/sources/whatsapp/Connector.java:78-82 — before extracting anything, compare `backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/Connector.java` and `backend/components/whatsapp/connector/src/main/java/co/airy/core/sources/whatsapp/Connector.java` 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. 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 `backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/Connector.java:92` 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 first that the copies are not typed on the same thing: `SendMessageRequest` names `co.airy.core.sources.facebook.dto.SendMessageRequest` in one and `co.airy.core.sources.google.model.SendMessageRequest` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/Connector.java:91` calls `add`, `pair`, `getId` and `backend/components/twilio/connector/src/main/java/co/airy/core/sources/twilio/Connector.java:73` 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 (3–5 lines × 3) backend/components/facebook/events-router/src/main/java/co/airy/core/sources/facebook/EventsRouter.java:75— backend/components/facebook/events-router/src/main/java/co/airy/core/sources/facebook/EventsRouter.java:75-77 | backend/components/twilio/events-router/src/main/java/co/airy/core/sources/twilio/EventsRouter.java:37-41 | backend/components/whatsapp/events-router/src/main/java/co/airy/core/sources/whatsapp/EventsRouter.java:62-66 — 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 6) backend/components/admin/src/main/java/co/airy/core/admin/ChannelsController.java:150— backend/components/admin/src/main/java/co/airy/core/admin/ChannelsController.java:150-154 | backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/Connector.java:187-191 | backend/components/google/connector/src/main/java/co/airy/core/sources/google/Connector.java:97-101 | backend/components/twilio/connector/src/main/java/co/airy/core/sources/twilio/Connector.java:98-102 | backend/components/viber/connector/src/main/java/co/airy/core/sources/viber/Connector.java:84-88 | backend/components/whatsapp/connector/src/main/java/co/airy/core/sources/whatsapp/Connector.java:107-111 — before extracting anything, compare `backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/Connector.java` and `backend/components/whatsapp/connector/src/main/java/co/airy/core/sources/whatsapp/Connector.java` 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 5) backend/components/google/events-router/src/main/java/co/airy/core/sources/google/EventsRouter.java:65— backend/components/google/events-router/src/main/java/co/airy/core/sources/google/EventsRouter.java:65-70 | backend/components/twilio/events-router/src/main/java/co/airy/core/sources/twilio/EventsRouter.java:106-111 | backend/components/unread-counter/src/main/java/co/airy/core/unread_counter/Stores.java:119-124 | backend/components/webhook/consumer/src/main/java/co/airy/core/webhook/consumer/Stores.java:55-60 | backend/components/whatsapp/events-router/src/main/java/co/airy/core/sources/whatsapp/EventsRouter.java:145-150 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. 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 (77–78 lines × 2) REDACTED:18— REDACTED:18-95 | REDACTED:16-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 `REDACTED:18` 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) REDACTED:331— REDACTED:331-346 | REDACTED:363-378 | REDACTED:392-407 — 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.
Unstable project //backend/model/event:event — //backend/model/event:event has instability 0.88 with 1 dependents.
P12 · CI test-gate honesty· Coverage collected but not gated · ×1
Coverage collected but not gated — CI collects a coverage report but no step enforces a minimum — coverage could halve and CI stays green. Add a step that fails the build when coverage drops below a floor (your coverage tool's minimum-threshold flag, or a coverage-gate action) so the number guards something. What was searched, so you can tell an absence from a miss: this repository's CI files AND its coverage configuration — the well-known coverage and test-runner config files, read at the repository root and inside workspace package directories two levels down, so a floor declared beside the tests rather than in the pipeline is credited — matched against the threshold settings this check knows by name. A floor set in your coverage service's web UI rather than in a committed file, or under a setting whose name is not one of those, is not seen here.
Duplication concentrated across 11 sibling directories (35 clone groups) frontend/control-center/src/pages/Apps/index.tsx:14— 35 duplicated blocks under frontend/control-center/src/pages/ have copies in at least two of the sibling directories Apps, Catalog, Connectors, Inbox, LLMConsumers, LLMs (+5 more sibling(s) not listed) — 27 of them are reported below, and 8 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 35 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 35 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 35 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 3 sibling directories (33 clone groups) frontend/control-center/src/components/TopBar/index.tsx:1— 33 duplicated blocks under frontend/ have copies in at least two of the sibling directories chat-plugin, control-center, inbox — 20 of them are reported below, and 13 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 33 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 33 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 33 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 5 sibling directories (13 clone groups) lib/typescript/render/providers/chatplugin/components/RichCard/index.tsx:27— 13 duplicated blocks under lib/typescript/render/providers/ have copies in at least two of the sibling directories chatplugin, google, meta, twilio, viber — 10 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 13 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 13 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 13 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 7 sibling directories (11 clone groups) frontend/control-center/src/pages/Connectors/Providers/Google/GoogleConnect.tsx:17— 11 duplicated blocks under frontend/control-center/src/pages/Connectors/Providers/ have copies in at least two of the sibling directories Airy, Facebook, Google, Instagram, Twilio, Viber (+1 more sibling(s) not listed) — 9 of them are reported below, and 2 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 11 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 11 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 11 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 3 sibling directories (10 clone groups) frontend/chat-plugin/lib/src/config.ts:7— 10 duplicated blocks under the repository root have copies in at least two of the sibling directories backend, frontend, lib — 7 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 10 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 10 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 10 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Wholesale file copy (212 identical lines × 2 files) frontend/control-center/src/components/TopBar/index.tsx:1— frontend/control-center/src/components/TopBar/index.tsx:1 · frontend/inbox/src/components/TopBar/index.tsx:1 — these 2 files are line-for-line copies of one another — 212 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 (104 matched lines × 2 locations) · ×1
Duplicated block with local edits (104 matched lines × 2 locations) frontend/control-center/src/pages/Schemas/SchemaItem/SchemaDescription/EnrichedSchemaSection/index.tsx:140— frontend/control-center/src/pages/Schemas/SchemaItem/SchemaDescription/EnrichedSchemaSection/index.tsx:140 · frontend/control-center/src/pages/Schemas/SchemaItem/SchemaDescription/SchemaSection/index.tsx:109 — the two spans are one implementation copied and then locally edited — 535 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (88 matched lines × 2 locations) · ×1
Duplicated block with local edits (88 matched lines × 2 locations) frontend/control-center/src/pages/Connectors/Providers/Google/GoogleConnect.tsx:17— frontend/control-center/src/pages/Connectors/Providers/Google/GoogleConnect.tsx:17 · frontend/control-center/src/pages/Connectors/Providers/Viber/ViberConnect.tsx:13 — the two spans are one implementation copied and then locally edited — 576 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 (86 matched lines × 2 locations) · ×1
Duplicated block with local edits (86 matched lines × 2 locations) frontend/inbox/src/reducers/data/conversations/index.ts:65— frontend/inbox/src/reducers/data/conversations/index.ts:65 · frontend/inbox/src/reducers/data/conversationsFilter/index.ts:39 — the two spans are one implementation copied and then locally edited — 467 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 (82 lines × 2 locations) frontend/control-center/src/pages/Apps/index.tsx:14— frontend/control-center/src/pages/Apps/index.tsx:14 · frontend/control-center/src/pages/Connectors/index.tsx:14 — 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 (72 matched lines × 2 locations) · ×1
Duplicated block with local edits (72 matched lines × 2 locations) frontend/inbox/src/pages/Contacts/ContactInformation/index.tsx:91— frontend/inbox/src/pages/Contacts/ContactInformation/index.tsx:91 · frontend/inbox/src/pages/Inbox/Messenger/ConversationMetadata/index.tsx:162 — the two spans are one implementation copied and then locally edited — 424 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 (70 matched lines × 2 locations) · ×1
Duplicated block with local edits (70 matched lines × 2 locations) frontend/control-center/src/pages/Streams/ListMode/ListMode.tsx:35— frontend/control-center/src/pages/Streams/ListMode/ListMode.tsx:35 · frontend/control-center/src/pages/Topics/ListMode/ListMode.tsx:30 — the two spans are one implementation copied and then locally edited — 435 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (55 matched lines × 2 locations) · ×1
Duplicated block with local edits (55 matched lines × 2 locations) frontend/control-center/src/actions/channel/index.ts:28— frontend/control-center/src/actions/channel/index.ts:28 · frontend/inbox/src/actions/channel/index.ts:31 — the two spans are one implementation copied and then locally edited — 578 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 (52 lines × 2 locations) lib/typescript/components/cta/Button/index.tsx:22— lib/typescript/components/cta/Button/index.tsx:22 · lib/typescript/components/cta/SmartButton/index.tsx:26 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (50 lines × 2 locations) frontend/control-center/src/reducers/data/channels/index.ts:7— frontend/control-center/src/reducers/data/channels/index.ts:7 · frontend/inbox/src/reducers/data/channels/index.ts:7 — 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 (49 lines × 2 locations) lib/typescript/render/providers/chatplugin/components/RichCard/index.tsx:27— lib/typescript/render/providers/chatplugin/components/RichCard/index.tsx:27 · lib/typescript/render/providers/google/components/RichCard/index.tsx:18 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (47 lines × 2 locations) frontend/control-center/src/pages/Connectors/Providers/Facebook/Messenger/FacebookConnect.tsx:13— frontend/control-center/src/pages/Connectors/Providers/Facebook/Messenger/FacebookConnect.tsx:13 · frontend/control-center/src/pages/Connectors/Providers/WhatsappBusinessCloud/WhatsappConnect.tsx:13 — 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 (43 matched lines × 2 locations) · ×1
Duplicated block with local edits (43 matched lines × 2 locations) frontend/control-center/src/pages/Schemas/SchemaItem/SchemaInfo.tsx:37— frontend/control-center/src/pages/Schemas/SchemaItem/SchemaInfo.tsx:37 · frontend/control-center/src/pages/Streams/StreamItem/StreamInfo.tsx:24 — the two spans are one implementation copied and then locally edited — 323 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) lib/typescript/components/general/FilterBar/FilterDropdown/index.tsx:36— lib/typescript/components/general/FilterBar/FilterDropdown/index.tsx:36 · lib/typescript/components/inputs/Dropdown/index.tsx:29 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (41 lines × 2 locations) lib/typescript/render/providers/meta/MetaRender.tsx:244— lib/typescript/render/providers/meta/MetaRender.tsx:244 · lib/typescript/render/providers/meta/MetaRender.tsx:455 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (38 lines × 2 locations) frontend/control-center/src/pages/Schemas/JoinMode/PhaseOne.tsx:79— frontend/control-center/src/pages/Schemas/JoinMode/PhaseOne.tsx:79 · frontend/control-center/src/pages/Schemas/JoinMode/PhaseOne.tsx:144 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (37 lines × 2 locations) lib/typescript/render/providers/chatplugin/ChatPluginRender.tsx:77— lib/typescript/render/providers/chatplugin/ChatPluginRender.tsx:77 · lib/typescript/render/providers/meta/MetaRender.tsx:340 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (36 matched lines × 2 locations) · ×1
Duplicated block with local edits (36 matched lines × 2 locations) frontend/chat-plugin/lib/src/airyRenderProps/AiryInputBar/InputSelector/index.tsx:20— frontend/chat-plugin/lib/src/airyRenderProps/AiryInputBar/InputSelector/index.tsx:20 · frontend/inbox/src/pages/Inbox/MessageInput/InputSelector.tsx:24 — the two spans are one implementation copied and then locally edited — 241 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 (36 lines × 2 locations) lib/typescript/render/providers/chatplugin/chatPluginModel.ts:59— lib/typescript/render/providers/chatplugin/chatPluginModel.ts:59 · lib/typescript/render/providers/google/googleModel.ts:28 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.
Duplicated block (35 lines × 2 locations) frontend/control-center/src/pages/Connectors/ConnectedChannelsList/DisableModal/index.tsx:36— frontend/control-center/src/pages/Connectors/ConnectedChannelsList/DisableModal/index.tsx:36 · frontend/control-center/src/pages/Webhooks/UnsubscribeModal/index.tsx:37 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (34 lines × 2 locations) frontend/control-center/src/pages/Connectors/Providers/Google/GoogleBusinessMessagesRequirementsDialog/index.tsx:13— frontend/control-center/src/pages/Connectors/Providers/Google/GoogleBusinessMessagesRequirementsDialog/index.tsx:13 · frontend/control-center/src/pages/Connectors/Providers/Instagram/InstagramRequirementsDialog/index.tsx:13 — 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 (34 matched lines × 2 locations) · ×1
Duplicated block with local edits (34 matched lines × 2 locations) frontend/control-center/src/pages/Schemas/SchemaItem/SchemaDescription/EnrichedSchemaSection/index.tsx:71— frontend/control-center/src/pages/Schemas/SchemaItem/SchemaDescription/EnrichedSchemaSection/index.tsx:71 · frontend/control-center/src/pages/Schemas/SchemaItem/SchemaDescription/SchemaSection/index.tsx:64 — the two spans are one implementation copied and then locally edited — 225 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 (31 matched lines × 2 locations) · ×1
Duplicated block with local edits (31 matched lines × 2 locations) frontend/control-center/src/pages/Connectors/ConnectedChannelsList/index.tsx:124— frontend/control-center/src/pages/Connectors/ConnectedChannelsList/index.tsx:124 · frontend/control-center/src/pages/Inbox/ChannelsList/index.tsx:120 — the two spans are one implementation copied and then locally edited — 193 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 (31 lines × 2 locations) REDACTED:147— REDACTED:147 · REDACTED:178 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (30 lines × 2 locations) frontend/control-center/src/pages/Connectors/Providers/Facebook/Messenger/FacebookMessengerRequirementsDialog/index.tsx:16— frontend/control-center/src/pages/Connectors/Providers/Facebook/Messenger/FacebookMessengerRequirementsDialog/index.tsx:16 · frontend/control-center/src/pages/Connectors/Providers/Instagram/InstagramRequirementsDialog/index.tsx:17 — 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 (27 lines × 3 locations) frontend/control-center/src/pages/Connectors/Providers/Facebook/Messenger/FacebookConnect.tsx:141— frontend/control-center/src/pages/Connectors/Providers/Facebook/Messenger/FacebookConnect.tsx:141 · frontend/control-center/src/pages/Connectors/Providers/Google/GoogleConnect.tsx:135 · frontend/control-center/src/pages/Connectors/Providers/WhatsappBusinessCloud/WhatsappConnect.tsx:137 — the 3 copies are spread across 3 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication· Duplicated block with local edits (26 matched lines × 2 locations) · ×1
Duplicated block with local edits (26 matched lines × 2 locations) frontend/chat-plugin/lib/src/components/dragAndDrop/index.tsx:11— frontend/chat-plugin/lib/src/components/dragAndDrop/index.tsx:11 · frontend/inbox/src/pages/Inbox/Messenger/MessengerContainer/index.tsx:115 — the two spans are one implementation copied and then locally edited — 183 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 (25 lines × 2 locations) frontend/control-center/src/pages/Connectors/Providers/Airy/ChatPlugin/sections/ConnectNewChatPlugin.tsx:51— frontend/control-center/src/pages/Connectors/Providers/Airy/ChatPlugin/sections/ConnectNewChatPlugin.tsx:51 · frontend/control-center/src/pages/Connectors/Providers/Airy/ChatPlugin/sections/CreateUpdateSection/CreateUpdateSection.tsx:57 — 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.
Boundary violation [package:third-party-deep-import] frontend/control-center/src/actions/streams/index.ts:5— frontend/control-center/src/actions/streams/index.ts:5 imports react-markdown/lib/ast-to-react, 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.
Complex function metaOutbound (cyclomatic 50, cognitive 64) lib/typescript/render/providers/meta/MetaRender.tsx:342— metaOutbound has cyclomatic complexity 50 and cognitive complexity 64; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 Sidebar (cyclomatic 42, cognitive 40) frontend/control-center/src/components/Sidebar/index.tsx:41— Sidebar has cyclomatic complexity 42 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 CustomiseSection (cyclomatic 41, cognitive 40) frontend/control-center/src/pages/Connectors/Providers/Airy/ChatPlugin/sections/CustomiseSection/CustomiseSection.tsx:23— CustomiseSection has cyclomatic complexity 41 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 InputOptions (cyclomatic 39, cognitive 26) frontend/inbox/src/pages/Inbox/MessageInput/InputOptions.tsx:41— InputOptions has cyclomatic complexity 39 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 lastMessageIsIcon (cyclomatic 33, cognitive 26) lib/typescript/render/SourceMessagePreview.tsx:158— lastMessageIsIcon has cyclomatic complexity 33 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 metaInbound (cyclomatic 32, cognitive 39) lib/typescript/render/providers/meta/MetaRender.tsx:220— metaInbound has cyclomatic complexity 32 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 render (cyclomatic 32, cognitive 11) lib/typescript/render/providers/meta/MetaRender.tsx:37— render has cyclomatic complexity 32 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function ColorSection (cyclomatic 31, cognitive 30) frontend/control-center/src/pages/Connectors/Providers/Airy/ChatPlugin/sections/CustomiseSection/ColorSection/index.tsx:36— ColorSection has cyclomatic complexity 31 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 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 lastMessageIsText (cyclomatic 30, cognitive 29) lib/typescript/render/SourceMessagePreview.tsx:48— lastMessageIsText has cyclomatic complexity 30 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 (anonymous) (cyclomatic 27, cognitive 32) lib/typescript/render/providers/twilio/TwilioRender.tsx:50— (anonymous) has cyclomatic complexity 27 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 ConnectorConfig (cyclomatic 27, cognitive 20) frontend/control-center/src/pages/Connectors/ConnectorConfig/index.tsx:38— ConnectorConfig has cyclomatic complexity 27 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 InputToggleSection (cyclomatic 25, cognitive 24) REDACTED:40— InputToggleSection has cyclomatic complexity 25 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 mapContent (cyclomatic 24, cognitive 28) lib/typescript/render/providers/chatplugin/ChatPluginRender.tsx:79— mapContent has cyclomatic complexity 24 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 MessageInput (cyclomatic 24, cognitive 22) frontend/inbox/src/pages/Inbox/MessageInput/index.tsx:58— MessageInput has cyclomatic complexity 24 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 ItemInfo (cyclomatic 24, cognitive 18) frontend/control-center/src/pages/Status/ComponentListItem/ItemInfo.tsx:31— ItemInfo has cyclomatic complexity 24 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 sendMessage (cyclomatic 23, cognitive 29) frontend/inbox/src/pages/Inbox/MessageInput/index.tsx:234— sendMessage has cyclomatic complexity 23 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function googleInbound (cyclomatic 22, cognitive 20) lib/typescript/render/providers/google/GoogleRender.tsx:60— googleInbound has cyclomatic complexity 22 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 (anonymous) (cyclomatic 21, cognitive 27) frontend/control-center/src/pages/Connectors/ConfigureConnector/SetConfigInputs/SetConfigInputs.tsx:25— (anonymous) has cyclomatic complexity 21 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function getTemplateConfig (cyclomatic 19, cognitive 18) frontend/control-center/src/pages/Connectors/Providers/Airy/ChatPlugin/sections/InstallSection/InstallSection.tsx:49— getTemplateConfig has cyclomatic complexity 19 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 TopBar (cyclomatic 18, cognitive 17) frontend/control-center/src/components/TopBar/index.tsx:37— TopBar has cyclomatic complexity 18 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 18, cognitive 17) lib/typescript/render/providers/meta/MetaRender.tsx:143— (anonymous) has cyclomatic complexity 18 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function ContactDetails (cyclomatic 18, cognitive 14) frontend/inbox/src/components/ContactDetails/index.tsx:44— ContactDetails has cyclomatic complexity 18 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 allReducer (cyclomatic 18, cognitive 10) frontend/inbox/src/reducers/data/conversations/index.ts:184— allReducer has cyclomatic complexity 18 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 17, cognitive 19) frontend/inbox/src/selectors/conversations.ts:81— (anonymous) has cyclomatic complexity 17 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function SideColumnContent (cyclomatic 17, cognitive 16) frontend/control-center/src/pages/Catalog/CatalogItemDetails/index.tsx:184— SideColumnContent has cyclomatic complexity 17 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 TopBar (cyclomatic 17, cognitive 16) frontend/inbox/src/components/TopBar/index.tsx:38— TopBar has cyclomatic complexity 17 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 FacebookConnect (cyclomatic 17, cognitive 15) frontend/control-center/src/pages/Connectors/Providers/Facebook/Messenger/FacebookConnect.tsx:23— FacebookConnect has cyclomatic complexity 17 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function WhatsappConnect (cyclomatic 17, cognitive 15) frontend/control-center/src/pages/Connectors/Providers/WhatsappBusinessCloud/WhatsappConnect.tsx:23— WhatsappConnect has cyclomatic complexity 17 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function GoogleConnect (cyclomatic 16, cognitive 14) frontend/control-center/src/pages/Connectors/Providers/Google/GoogleConnect.tsx:27— GoogleConnect has cyclomatic complexity 16 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 googleOutbound (cyclomatic 15, cognitive 17) lib/typescript/render/providers/google/GoogleRender.tsx:152— googleOutbound has cyclomatic complexity 15 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function ConnectorWrapper (cyclomatic 15, cognitive 14) frontend/control-center/src/pages/Connectors/ConnectorWrapper/index.tsx:38— ConnectorWrapper has cyclomatic complexity 15 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 Tooltip (cyclomatic 15, cognitive 14) lib/typescript/components/tooltip/index.tsx:20— Tooltip has cyclomatic complexity 15 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 Creation (cyclomatic 15, cognitive 10) frontend/control-center/src/pages/Streams/Creation/index.tsx:31— Creation has cyclomatic complexity 15 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function ChatPluginConnect (cyclomatic 14, cognitive 13) frontend/control-center/src/pages/Connectors/Providers/Airy/ChatPlugin/ChatPluginConnect.tsx:46— ChatPluginConnect has cyclomatic complexity 14 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function SubscriptionModal (cyclomatic 14, cognitive 13) frontend/control-center/src/pages/Webhooks/SubscriptionModal/index.tsx:24— SubscriptionModal has cyclomatic complexity 14 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 14, cognitive 13) frontend/inbox/src/components/IconChannel/index.tsx:93— (anonymous) has cyclomatic complexity 14 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function TwilioConnect (cyclomatic 14, cognitive 12) frontend/control-center/src/pages/Connectors/Providers/Twilio/TwilioConnect.tsx:28— TwilioConnect has cyclomatic complexity 14 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function ViberConnect (cyclomatic 14, cognitive 12) frontend/control-center/src/pages/Connectors/Providers/Viber/ViberConnect.tsx:23— ViberConnect has cyclomatic complexity 14 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function WhatsAppInteractive (cyclomatic 14, cognitive 10) lib/typescript/render/providers/meta/components/WhatsAppInteractive/index.tsx:16— WhatsAppInteractive has cyclomatic complexity 14 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function Chat (cyclomatic 13, cognitive 12) frontend/chat-plugin/lib/src/components/chat/index.tsx:56— Chat has cyclomatic complexity 13 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files· frontend/inbox/src/pages/Inbox/MessageInput/index.tsx · ×1
frontend/inbox/src/pages/Inbox/MessageInput/index.tsx: 516 lines of code frontend/inbox/src/pages/Inbox/MessageInput/index.tsx:1— frontend/inbox/src/pages/Inbox/MessageInput/index.tsx has 516 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· frontend/control-center/src/pages/Streams/Creation/index.tsx · ×1
frontend/control-center/src/pages/Streams/Creation/index.tsx: 501 lines of code frontend/control-center/src/pages/Streams/Creation/index.tsx:1— frontend/control-center/src/pages/Streams/Creation/index.tsx has 501 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/typescript/render/providers/meta/MetaRender.tsx · ×1
lib/typescript/render/providers/meta/MetaRender.tsx: 473 lines of code lib/typescript/render/providers/meta/MetaRender.tsx:1— lib/typescript/render/providers/meta/MetaRender.tsx has 473 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· lib/typescript/components/inputs/Input/index.tsx · ×1
lib/typescript/components/inputs/Input/index.tsx: 452 lines of code lib/typescript/components/inputs/Input/index.tsx:1— lib/typescript/components/inputs/Input/index.tsx has 452 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· frontend/control-center/src/pages/Connectors/Providers/Airy/ChatPlugin/sections/CustomiseSection/ColorSection/index.tsx · ×1
frontend/control-center/src/pages/Connectors/Providers/Airy/ChatPlugin/sections/CustomiseSection/ColorSection/index.tsx: 438 lines of code frontend/control-center/src/pages/Connectors/Providers/Airy/ChatPlugin/sections/CustomiseSection/ColorSection/index.tsx:1— frontend/control-center/src/pages/Connectors/Providers/Airy/ChatPlugin/sections/CustomiseSection/ColorSection/index.tsx has 438 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
No typecheck script — test ✓ · lint ✓ · typecheck ✗ — read from this repository's REDACTED scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
Dead file (~2580 LoC) lib/typescript/translations/translations.ts— no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (lib/typescript/translations/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~554 LoC) lib/typescript/render/providers/meta/MetaRender.tsx— no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (lib/typescript/render/renderProviders.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 (~374 LoC) lib/typescript/httpclient/src/client.ts— no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (lib/typescript/httpclient/src/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~351 LoC) frontend/chat-plugin/lib/src/components/chat/index.tsx— no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (frontend/chat-plugin/lib/src/AiryChatPlugin.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 (~327 LoC) lib/typescript/render/providers/meta/MetaModel.ts— no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 11 in-repo import(s) from 11 other file(s) do name it (lib/typescript/render/components/Image/index.tsx, lib/typescript/render/providers/meta/MetaRender.tsx, lib/typescript/render/providers/meta/components/ButtonTemplate/index.tsx and 8 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~278 LoC) frontend/chat-plugin/lib/src/airyRenderProps/AiryInputBar/index.tsx— no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (frontend/chat-plugin/lib/src/components/chat/index.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 (~250 LoC) lib/typescript/render/SourceMessagePreview.tsx— no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (lib/typescript/render/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~245 LoC) lib/typescript/render/providers/chatplugin/ChatPluginRender.tsx— no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (lib/typescript/render/renderProviders.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 (~236 LoC) lib/typescript/render/providers/google/GoogleRender.tsx— no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (lib/typescript/render/renderProviders.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 (~216 LoC) lib/typescript/render/providers/twilio/TwilioRender.tsx— no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (lib/typescript/render/renderProviders.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 (~188 LoC) lib/typescript/components/general/AudioClip/index.tsx— no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (lib/typescript/components/general/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~171 LoC) frontend/control-center/src/pages/Inbox/ChannelsList/index.tsx— no import path from any entry point (8 application, 4 tooling, 13 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 (~150 LoC) lib/typescript/render/providers/chatplugin/chatPluginModel.ts— no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 4 in-repo import(s) from 4 other file(s) do name it (lib/typescript/render/providers/chatplugin/ChatPluginRender.tsx, lib/typescript/render/providers/chatplugin/components/RichCard/Media/index.tsx, lib/typescript/render/providers/chatplugin/components/RichCard/index.tsx and 1 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~139 LoC) lib/typescript/components/general/Carousel/index.tsx— no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (lib/typescript/components/general/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~128 LoC) frontend/chat-plugin/lib/src/websocket/index.ts— no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (frontend/chat-plugin/lib/src/components/chat/index.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 (~127 LoC) lib/typescript/components/tooltip/index.tsx— no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (lib/typescript/components/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~126 LoC) lib/typescript/render/providers/google/googleModel.ts— no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 5 in-repo import(s) from 5 other file(s) do name it (lib/typescript/render/providers/google/GoogleRender.tsx, lib/typescript/render/providers/google/components/RichCard/Media/index.tsx, lib/typescript/render/providers/google/components/RichCard/index.tsx and 2 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~112 LoC) lib/typescript/render/services/mediaAttachments.ts— no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (lib/typescript/render/services/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~111 LoC) lib/typescript/components/general/FilterBar/FilterDropdown/index.tsx— no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (lib/typescript/components/general/FilterBar/index.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 (~109 LoC) lib/typescript/components/general/AudioClip/services/drawCanvasPaths.ts— no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (lib/typescript/components/general/AudioClip/services/index.ts, lib/typescript/components/general/AudioClip/services/progressBar.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 (~106 LoC) frontend/control-center/src/pages/Inbox/ChannelsList/ChannelListItem/index.tsx— no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (frontend/control-center/src/pages/Inbox/ChannelsList/index.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 (~103 LoC) frontend/chat-plugin/lib/src/AiryChatPlugin.tsx— no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (frontend/chat-plugin/lib/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~94 LoC) frontend/chat-plugin/lib/src/airyRenderProps/AiryBubble/index.tsx— no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (frontend/chat-plugin/lib/src/components/chat/index.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 (~92 LoC) lib/typescript/websocketclient/payload.ts— no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (lib/typescript/websocketclient/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~87 LoC) lib/typescript/components/cta/Button/index.tsx— no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (lib/typescript/components/cta/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~85 LoC) lib/typescript/render/providers/meta/components/WhatsAppTemplate/index.tsx— no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (lib/typescript/render/providers/meta/components/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~83 LoC) frontend/control-center/src/pages/Catalog/CatalogSearchBar/CatalogSearchBar.tsx— no import path from any entry point (8 application, 4 tooling, 13 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 (~81 LoC) lib/typescript/render/providers/meta/components/WhatsAppInteractive/index.tsx— no import path from any entry point (8 application, 4 tooling, 13 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (lib/typescript/render/providers/meta/components/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Unused dependency '@hot-loader/react-dom' REDACTED:55— Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@svgr/plugin-svgo' REDACTED:56— Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@testing-library/user-event' REDACTED:12— Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'dotenv-webpack' REDACTED:76— Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'emoji-mart' REDACTED:20— Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'linkifyjs' REDACTED:25— Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'minimist' REDACTED:84— Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'preact' REDACTED:27— Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'react-refresh' REDACTED:37— Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'react-test-renderer' REDACTED:87— Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'node-fetch' backend/components/schema-registry-manager/src/REDACTED:8— Declared in backend/components/schema-registry-manager/src/REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
SC1 · Supply-chain hygiene· JavaScript dependencies are not locked · ×1
JavaScript dependencies are not locked backend/components/schema-registry-manager/src/REDACTED:2— backend/components/schema-registry-manager/src/REDACTED declares dependencies that no committed lockfile resolves — there is no package-lock.json / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
X3 · Exception handling· Lost error (reports an error that is nil on this path) · ×1
Lost error (reports an error that is nil on this path) infrastructure/controller/pkg/endpoints/components_delete.go:49— `if deleteErr != nil` handles a failure of `deleteErr` but reports `err`, which the earlier `if err != nil { return … }` already proved nil here: the real failure is lost and a nil error is reported (or returned as success) in its place. Report `deleteErr`.
X3 · Exception handling· Discarded error (an error-returning call as a bare statement) · ×1
Discarded error (an error-returning call as a bare statement) cli/pkg/helm/helm.go:104— `h.cleanupJob()` returns an error, and the statement drops it: when `h.cleanupJob` fails nothing records it and the code after it runs as if it had succeeded. Check it (`if err := h.cleanupJob(); err != nil { … }`) and return or log it with what was being done, or assign it to `_` with a comment saying why the failure cannot matter.
Orphaned file frontend/control-center/src/pages/Connectors/Providers/Airy/ChatPlugin/sections/CustomiseSection/ColorSection/index.tsx: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 REDACTED: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 backend/components/communication/src/main/java/co/airy/core/communication/Stores.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/typescript/render/providers/meta/MetaRender.tsx: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 backend/model/contact/src/main/java/co/airy/model/contact/Contact.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file REDACTED: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/typescript/components/inputs/Input/index.tsx: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 frontend/control-center/src/pages/Connectors/Providers/Airy/ChatPlugin/sections/CustomiseSection/CustomiseSection.tsx: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 frontend/control-center/src/pages/Catalog/CatalogItemDetails/index.tsx: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 backend/components/contacts/src/main/java/co/airy/core/contacts/Stores.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file backend/components/communication/src/main/java/co/airy/core/communication/ConversationsController.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file frontend/control-center/src/pages/Catalog/CatalogCard/index.tsx: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/typescript/httpclient/src/client.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file frontend/inbox/src/pages/Inbox/Messenger/ConversationMetadata/index.tsx: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 frontend/chat-plugin/lib/src/components/chat/index.tsx: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 frontend/inbox/src/components/TopBar/index.tsx: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 frontend/control-center/src/components/TopBar/index.tsx: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 backend/components/admin/src/main/java/co/airy/core/admin/Stores.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file frontend/control-center/src/pages/Catalog/index.tsx: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 backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/api/Api.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file frontend/inbox/src/pages/Inbox/QuickFilter/Popup.tsx: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 backend/components/contacts/src/main/java/co/airy/core/contacts/ContactsController.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file backend/components/sources-api/src/main/java/co/airy/core/sources/api/Stores.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file frontend/inbox/src/reducers/data/conversations/index.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/ChannelsController.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Interpolated log message defeats structured logging lib/java/spring/async/src/main/java/co/airy/spring/async/AsyncExecutorConfig.java:36— `info` at line 36 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging REDACTED:300— `info` at line 300 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging REDACTED:301— `info` at line 301 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging lib/java/kafka/core/src/main/java/co/airy/kafka/core/KafkaConsumerWrapper.java:75— `error` at line 75 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging backend/model/contact/src/main/java/co/airy/model/contact/Contact.java:259— `error` at line 259 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging backend/model/contact/src/main/java/co/airy/model/contact/Contact.java:302— `error` at line 302 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging backend/components/whatsapp/events-router/src/main/java/co/airy/core/sources/whatsapp/EventsRouter.java:100— `warn` at line 100 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging backend/components/whatsapp/events-router/src/main/java/co/airy/core/sources/whatsapp/EventsRouter.java:113— `warn` at line 113 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging backend/components/whatsapp/connector/src/main/java/co/airy/core/sources/whatsapp/Connector.java:67— `error` at line 67 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging backend/components/whatsapp/connector/src/main/java/co/airy/core/sources/whatsapp/Connector.java:80— `error` at line 80 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging backend/components/viber/connector/src/main/java/co/airy/core/sources/viber/Connector.java:62— `error` at line 62 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging backend/components/twilio/events-router/src/main/java/co/airy/core/sources/twilio/EventsRouter.java:83— `warn` at line 83 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging backend/components/twilio/connector/src/main/java/co/airy/core/sources/twilio/Connector.java:64— `error` at line 64 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging backend/components/twilio/connector/src/main/java/co/airy/core/sources/twilio/Connector.java:76— `error` at line 76 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging backend/components/rasa/src/main/java/co/airy/core/rasa_connector/RasaConnectorService.java:45— `info` at line 45 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging backend/components/rasa/src/main/java/co/airy/core/rasa_connector/RasaConnectorService.java:49— `error` at line 49 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging backend/components/rasa/src/main/java/co/airy/core/rasa_connector/RasaConnectorService.java:63— `error` at line 63 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging backend/components/installer/src/main/java/co/airy/core/api/components/installer/HelmJobHandler.java:169— `error` at line 169 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging backend/components/installer/src/main/java/co/airy/core/api/components/installer/InstallerController.java:40— `error` at line 40 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging backend/components/installer/src/main/java/co/airy/core/api/components/installer/InstallerController.java:54— `error` at line 54 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging backend/components/installer/src/main/java/co/airy/core/api/components/installer/InstallerController.java:67— `error` at line 67 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging backend/components/installer/src/main/java/co/airy/core/api/components/installer/InstallerHandler.java:59— `info` at line 59 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging backend/components/installer/src/main/java/co/airy/core/api/components/installer/InstallerHandler.java:80— `info` at line 80 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging backend/components/installer/src/main/java/co/airy/core/api/components/installer/InstallerHandlerCacheManager.java:94— `error` at line 94 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging backend/components/ibm-watson-assistant/src/main/java/co/airy/core/ibm_watson_assistant_connector/IbmWatsonAssistantConnectorService.java:54— `error` at line 54 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Duplicated predicate REDACTED:29— `kafkaURL == "" || schemaRegistryURL == "" || topicName == ""` appears character-identically in 2 files — REDACTED, REDACTED. 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 backend/components/whatsapp/connector/src/main/java/co/airy/core/sources/whatsapp/Stores.java:69— `"whatsapp".equals(channel.getSource()) && channel.getConnectionState().equals(ChannelConnectionState.CONNECTED)` appears character-identically in 2 files — backend/components/whatsapp/connector/src/main/java/co/airy/core/sources/whatsapp/Stores.java, backend/components/whatsapp/events-router/src/main/java/co/airy/core/sources/whatsapp/EventsRouter.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate backend/components/chat-plugin/src/main/java/co/airy/core/chat_plugin/config/WebSocketConfig.java:67— `authToken != null && authToken.startsWith("Bearer")` appears character-identically in 2 files — backend/components/chat-plugin/src/main/java/co/airy/core/chat_plugin/config/WebSocketConfig.java, lib/java/spring/auth/src/main/java/co/airy/spring/auth/token/AuthenticationFilter.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate backend/components/twilio/connector/src/main/java/co/airy/core/sources/twilio/Stores.java:61— `channel.getSource().startsWith("twilio") && channel.getConnectionState().equals(ChannelConnectionState.CONNECTED)` appears character-identically in 2 files — backend/components/twilio/connector/src/main/java/co/airy/core/sources/twilio/Stores.java, backend/components/twilio/events-router/src/main/java/co/airy/core/sources/twilio/EventsRouter.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate lib/java/spring/web/src/main/java/co/airy/spring/web/filters/HttpPostLogFilter.java:47— `isFirstRequest && !(request instanceof ContentCachingRequestWrapper)` appears character-identically in 2 files — lib/java/spring/web/src/main/java/co/airy/spring/web/filters/HttpPostLogFilter.java, lib/java/spring/web/src/main/java/co/airy/spring/web/filters/RequestLoggingFilter.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate backend/components/cognigy/src/main/java/co/airy/core/cognigy_connector/Stores.java:46— `message != null && isNewMessage(message) && message.getIsFromContact()` appears character-identically in 3 files — backend/components/cognigy/src/main/java/co/airy/core/cognigy_connector/Stores.java, backend/components/ibm-watson-assistant/src/main/java/co/airy/core/ibm_watson_assistant_connector/Stores.java, backend/components/rasa/src/main/java/co/airy/core/rasa_connector/Stores.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/Stores.java:72— `sources.contains(channel.getSource()) && channel.getConnectionState().equals(ChannelConnectionState.CONNECTED)` appears character-identically in 2 files — backend/components/facebook/connector/src/main/java/co/airy/core/sources/facebook/Stores.java, backend/components/facebook/events-router/src/main/java/co/airy/core/sources/facebook/EventsRouter.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate backend/components/facebook/events-router/src/main/java/co/airy/core/sources/facebook/EventsRouter.java:160— `streams == null || !streams.state().isRunningOrRebalancing()` appears character-identically in 6 files — backend/components/facebook/events-router/src/main/java/co/airy/core/sources/facebook/EventsRouter.java, backend/components/google/events-router/src/main/java/co/airy/core/sources/google/EventsRouter.java, backend/components/twilio/events-router/src/main/java/co/airy/core/sources/twilio/EventsRouter.java, backend/components/unread-counter/src/main/java/co/airy/core/unread_counter/Stores.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate backend/components/chat-plugin/src/main/java/co/airy/core/chat_plugin/config/JwtAuthenticationFilter.java:48— `systemToken != null && systemToken.equals(token)` appears character-identically in 2 files — backend/components/chat-plugin/src/main/java/co/airy/core/chat_plugin/config/JwtAuthenticationFilter.java, lib/java/spring/auth/src/main/java/co/airy/spring/auth/token/AuthenticationFilter.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate frontend/control-center/src/pages/Connectors/Providers/Facebook/Messenger/FacebookConnect.tsx:54— `!(id.length > 5 && token != '') || (channel?.sourceChannelId === id && channel?.metadata?.pageToken === token && channel?.metadata?.name ===…` appears character-identically in 2 files — frontend/control-center/src/pages/Connectors/Providers/Facebook/Messenger/FacebookConnect.tsx, frontend/control-center/src/pages/Connectors/Providers/Instagram/InstagramConnect.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 frontend/inbox/src/reducers/data/conversations/index.ts:208— `action.payload.subject !== 'conversation' || !state.items[action.payload.identifier]` appears character-identically in 2 files — frontend/inbox/src/reducers/data/conversations/index.ts, frontend/inbox/src/reducers/data/conversationsFilter/index.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate frontend/control-center/src/pages/Connectors/ConnectedChannelsList/ChannelsListItem/index.tsx:39— `channel.source === 'twilio.sms' || channel.source === 'twilio.whatsapp'` appears character-identically in 3 files — frontend/control-center/src/pages/Connectors/ConnectedChannelsList/ChannelsListItem/index.tsx, frontend/control-center/src/pages/Inbox/ChannelsList/ChannelListItem/index.tsx, frontend/inbox/src/components/IconChannel/index.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 frontend/control-center/src/pages/Connectors/Providers/Facebook/Messenger/FacebookConnect.tsx:44— `channel?.sourceChannelId !== id && !!channel` appears character-identically in 3 files — frontend/control-center/src/pages/Connectors/Providers/Facebook/Messenger/FacebookConnect.tsx, frontend/control-center/src/pages/Connectors/Providers/Google/GoogleConnect.tsx, frontend/control-center/src/pages/Connectors/Providers/Instagram/InstagramConnect.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/typescript/components/general/FilterBar/FilterDropdown/index.tsx:52— `componentEl.current && !componentEl.current.contains(e.target)` appears character-identically in 2 files — lib/typescript/components/general/FilterBar/FilterDropdown/index.tsx, lib/typescript/components/inputs/Dropdown/index.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 frontend/chat-plugin/lib/src/airyRenderProps/AiryInputBar/InputSelector/index.tsx:32— `fileSelectorHeight >= textareaHeight && fileSelectorWidth > minImageHeight` appears character-identically in 2 files — frontend/chat-plugin/lib/src/airyRenderProps/AiryInputBar/InputSelector/index.tsx, frontend/inbox/src/pages/Inbox/MessageInput/InputSelector.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 frontend/control-center/src/components/TopBar/index.tsx:47— `localStorage.getItem('language') || Language.english` appears character-identically in 2 files — frontend/control-center/src/components/TopBar/index.tsx, frontend/inbox/src/components/TopBar/index.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/typescript/render/providers/chatplugin/ChatPluginRender.tsx:82— `message.content?.message && Object.entries(message.content?.message).length > 0` appears character-identically in 2 files — lib/typescript/render/providers/chatplugin/ChatPluginRender.tsx, lib/typescript/render/providers/meta/MetaRender.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 frontend/inbox/src/actions/messages/index.ts:81— `paginationData && paginationData.loading` appears character-identically in 2 files — frontend/inbox/src/actions/messages/index.ts, frontend/inbox/src/pages/Inbox/Messenger/MessageList/index.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 frontend/inbox/src/actions/messages/index.ts:80— `paginationData && paginationData.nextCursor` appears character-identically in 2 files — frontend/inbox/src/actions/messages/index.ts, frontend/inbox/src/pages/Inbox/Messenger/MessageList/index.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 frontend/chat-plugin/lib/src/airyRenderProps/AiryInputBar/InputSelector/index.tsx:59— `removeFileButton && removeFileButton.current` appears character-identically in 2 files — frontend/chat-plugin/lib/src/airyRenderProps/AiryInputBar/InputSelector/index.tsx, frontend/inbox/src/pages/Inbox/MessageInput/InputSelector.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 backend/components/schema-registry-manager/src/providers/karapace.ts:9— `response.error_code && response.error_code.toString().includes('404') && !topicName.includes('-value')` appears character-identically in 2 files — backend/components/schema-registry-manager/src/providers/karapace.ts, frontend/control-center/src/actions/streams/index.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate frontend/control-center/src/env.ts:13— `templatedState.API_HOST || process.env.API_HOST || location.origin` appears character-identically in 2 files — frontend/control-center/src/env.ts, frontend/inbox/src/env.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 frontend/control-center/src/pages/Schemas/SchemaItem/SchemaDescription/EnrichedSchemaSection/index.tsx:98— `typeof field.type === 'object' && !Array.isArray(field.type)` appears character-identically in 2 files — frontend/control-center/src/pages/Schemas/SchemaItem/SchemaDescription/EnrichedSchemaSection/index.tsx, frontend/control-center/src/pages/Schemas/SchemaItem/SchemaDescription/SchemaSection/index.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 frontend/inbox/src/pages/Inbox/MessageInput/AudioRecording/AudioStream.tsx:25— `window.AudioContext || window.webkitAudioContext` appears character-identically in 2 files — frontend/inbox/src/pages/Inbox/MessageInput/AudioRecording/AudioStream.tsx, lib/typescript/components/general/AudioClip/services/decodeAudioData.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 frontend/control-center/src/pages/Schemas/SchemaItem/SchemaDescription/EnrichedSchemaSection/index.tsx:76— `wrapperSection && wrapperSection.current` appears character-identically in 5 files — frontend/control-center/src/pages/Schemas/SchemaItem/SchemaDescription/EnrichedSchemaSection/index.tsx, frontend/control-center/src/pages/Schemas/SchemaItem/SchemaDescription/SchemaSection/index.tsx, frontend/control-center/src/pages/Status/ComponentListItem/index.tsx, frontend/control-center/src/pages/Streams/StreamItem/StreamDescription/StreamDescription.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.
No seccomp profile REDACTED:175— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:218— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile infrastructure/helm-chart/charts/ingress-controller/templates/letsencrypt.yaml:30— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile infrastructure/helm-chart/charts/ingress-controller/templates/letsencrypt.yaml:72— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:49— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:34— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
X7 · Silent fallback defaults· Pending state with no failure state · ×4
Pending state with no failure state frontend/inbox/src/pages/Inbox/MessageInput/AudioRecording/index.tsx:181— The view draws `<SimpleLoader/>` under `loading`, but `loading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
Pending state with no failure state frontend/control-center/src/pages/LLMs/index.tsx:64— The view draws `<AiryLoader height= width= position="relative"/>` under `llms ?. length === 0 && dataFetched`, but `llms` 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 frontend/control-center/src/pages/LLMConsumers/index.tsx:183— The view draws `<AiryLoader height= width= position="relative"/>` under `consumers ?. length === 0 && dataFetched`, but `consumers` 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 frontend/chat-plugin/lib/src/airyRenderProps/AiryInputBar/index.tsx:229— The view draws `loading file...` under `loadingFile`, but `loadingFile` 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.
D34 · Knowledge Freshness· Most significant orphaned file · ×3
Most significant orphaned file lib/typescript/translations/translations.ts:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file frontend/control-center/src/pages/Streams/Creation/index.tsx:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file frontend/inbox/src/pages/Inbox/MessageInput/index.tsx:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
No ADRs found REDACTED:1— No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `REDACTED` makes this repository a deployable product (line 1).
D21 · Naming Consistency· `conversationId` spells `Id` where 12 names in the project spell it `ID` · ×1
`conversationId` spells `Id` where 12 names in the project spell it `ID` REDACTED:137— 12 of 13 names in project github.com/airyhq/airy spell the token `ID` (12 of 13; unit: names in project github.com/airyhq/airy containing `ID`). Peers: main.produceFlinkOutput(groupID) (REDACTED:95); main.getFlinkResult(sessionID) (REDACTED:235); main.getFlinkResultConfluent(sessionID) (REDACTED:329); ApplicationCommunicationSendMessage.ConversationID (backend/components/flink-connector/src/types.go:4); FlinkOutput.SessionID (backend/components/flink-connector/src/types.go:20). Rename to `conversationID`. [rule N6]
D21 · Naming Consistency· `getAppExternalURL` spells `URL` where 41 names in the project spell it `Url` · ×1
`getAppExternalURL` spells `URL` where 41 names in the project spell it `Url` frontend/control-center/src/services/getAppExternalURL.ts:6— 41 of 43 names in project @airyhq/airy spell the token `Url` (41 of 43; unit: names in project @airyhq/airy containing `Url`). Peers: index.fallbackImageUrl (frontend/control-center/src/components/ChannelAvatar/index.tsx:45); index.fallbackImageUrl (frontend/inbox/src/components/ChannelAvatar/index.tsx:17); decodeAudioData.decodeAudioStream(audioUrl) (lib/typescript/components/general/AudioClip/services/decodeAudioData.ts:7); HttpClient.apiUrl (lib/typescript/httpclient/src/client.ts:124); HttpClient.loginUrl (lib/typescript/httpclient/src/client.ts:125). Rename to `getAppExternalUrl`. [rule N6]
D21 · Naming Consistency· `checkWithURLValidation` spells `URL` where 41 names in the project spell it `Url` · ×1
`checkWithURLValidation` spells `URL` where 41 names in the project spell it `Url` lib/typescript/components/inputs/Input/index.tsx:105— 41 of 43 names in project @airyhq/airy spell the token `Url` (41 of 43; unit: names in project @airyhq/airy containing `Url`). Peers: index.fallbackImageUrl (frontend/control-center/src/components/ChannelAvatar/index.tsx:45); index.fallbackImageUrl (frontend/inbox/src/components/ChannelAvatar/index.tsx:17); decodeAudioData.decodeAudioStream(audioUrl) (lib/typescript/components/general/AudioClip/services/decodeAudioData.ts:7); HttpClient.apiUrl (lib/typescript/httpclient/src/client.ts:124); HttpClient.loginUrl (lib/typescript/httpclient/src/client.ts:125). Rename to `checkWithUrlValidation`. [rule N6]
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion REDACTED:1— `(repository root)` (49717 LoC, 1035 module-visible types across 396 directories) overshoots its size bounds. 1 of 11 build unit(s) (Go, npm) overshoot their size bounds, lowering Project Cohesion to 8.2/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.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
Dormant codebase — 260 of 260 significant files have no living knowledge — the codebase as a whole is dormant, not 260 separate risks. Counted over 260 of the 993 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. Re-engage owners or document before change.
D40 · Network Egress Confinement· No network policy · ×1
No network policy — No Kubernetes NetworkPolicy (or Cilium policy) found. Without one, every pod can talk to every other pod and reach out to the internet by default. Add a default-deny policy and open only the flows you need.
No runtime threat detection — No runtime threat-detection engine (Tetragon TracingPolicy / Falco) is committed. These observe process, file and network activity in-kernel and can alert or kill on malicious behaviour a static scan cannot catch.
D42 · Runtime Threat Enforcement· No admission-control policy · ×1
No admission-control policy — No policy-enforcement gate (Kyverno / OPA Gatekeeper / PodSecurity admission) is committed. Admission control keeps workloads that violate your security baseline from ever reaching the cluster.
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.
Logging is not universal — Only 6/8 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `backend/components/schema-registry-manager/src`, `docs/cli-doc`.
No SAST REDACTED:3— No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 3 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
P3 · Security & performance tooling· Dependabot does not watch github-actions/gomod · ×1
Dependabot does not watch github-actions/gomod REDACTED:2— `REDACTED` schedules updates, but no `package-ecosystem` entry covers `github-actions`, `gomod`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entries to the `updates:` list.
No security response headers detected frontend/inbox/nginx.conf:32— None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `nginx.conf` is committed to this repository and declares the server that serves it, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.)
X2 · Cancellation propagation· Not all functions that make a request accept a context.Context or an AbortSignal · ×1
Not all functions that make a request accept a context.Context or an AbortSignal — Only 1/18 functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial) accept a context.Context or an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, a cancelled request, a shutdown, an expired deadline. Take a `signal` (Go: `ctx context.Context`) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
X5 · Nullable reference types· Strict null checking is not enabled everywhere the repository type-checks · ×1
Strict null checking is not enabled everywhere the repository type-checks — 1/3 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
Silent fallback default on error REDACTED:104— `getAuthCookie` turns a non-nil `err` into `return ""` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or return it. 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 `if` or in the doc comment, and the row stops firing.
Outdated: github.com/TwinProduction/go-color — `github.com/TwinProduction/go-color` is required at v1.0.0 in REDACTED, but v1.4.1 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/TwinProduction/go-color@v1.4.1 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/TwinProduction/go-color — `github.com/TwinProduction/go-color` is required at v1.0.0 in REDACTED, but v1.4.1 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/TwinProduction/go-color@v1.4.1 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/airyhq/airy — `github.com/airyhq/airy` is required at v0.0.0-20220525151558-d1b9cb353828 in REDACTED, but v1.22.17 is the module's current release — so this build is missing every fix published since, including any security fix. This crosses a major version — v0 releases carry no compatibility promise, so read the changelog before taking it. Run `go get github.com/airyhq/airy@v1.22.17 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/airyhq/airy — `github.com/airyhq/airy` is required at v0.0.0-20220525151558-d1b9cb353828 in REDACTED, but v1.22.17 is the module's current release — so this build is missing every fix published since, including any security fix. This crosses a major version — v0 releases carry no compatibility promise, so read the changelog before taking it. Run `go get github.com/airyhq/airy@v1.22.17 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/aws/aws-sdk-go-v2/config — `github.com/aws/aws-sdk-go-v2/config` is required at v1.15.7 in REDACTED, but v1.33.19 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/aws/aws-sdk-go-v2/config@v1.33.19 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/aws/aws-sdk-go-v2/config — `github.com/aws/aws-sdk-go-v2/config` is required at v1.15.7 in REDACTED, but v1.33.19 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/aws/aws-sdk-go-v2/config@v1.33.19 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/aws/aws-sdk-go-v2/service/ec2 — `github.com/aws/aws-sdk-go-v2/service/ec2` is required at v1.44.0 in REDACTED, but v1.348.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/aws/aws-sdk-go-v2/service/ec2@v1.348.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/aws/aws-sdk-go-v2/service/ec2 — `github.com/aws/aws-sdk-go-v2/service/ec2` is required at v1.44.0 in REDACTED, but v1.348.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/aws/aws-sdk-go-v2/service/ec2@v1.348.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/aws/aws-sdk-go-v2/service/eks — `github.com/aws/aws-sdk-go-v2/service/eks` is required at v1.21.1 in REDACTED, but v1.105.6 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/aws/aws-sdk-go-v2/service/eks@v1.105.6 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/aws/aws-sdk-go-v2/service/eks — `github.com/aws/aws-sdk-go-v2/service/eks` is required at v1.21.1 in REDACTED, but v1.105.6 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/aws/aws-sdk-go-v2/service/eks@v1.105.6 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/aws/aws-sdk-go-v2/service/iam — `github.com/aws/aws-sdk-go-v2/service/iam` is required at v1.18.5 in REDACTED, but v1.66.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/aws/aws-sdk-go-v2/service/iam@v1.66.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/aws/aws-sdk-go-v2/service/iam — `github.com/aws/aws-sdk-go-v2/service/iam` is required at v1.18.5 in REDACTED, but v1.66.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/aws/aws-sdk-go-v2/service/iam@v1.66.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/gorilla/mux — `github.com/gorilla/mux` is required at v1.8.0 in REDACTED, but v1.8.1 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/gorilla/mux@v1.8.1 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/gorilla/mux — `github.com/gorilla/mux` is required at v1.8.0 in REDACTED, but v1.8.1 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/gorilla/mux@v1.8.1 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/kr/pretty — `github.com/kr/pretty` is required at v0.3.0 in REDACTED, but v0.3.1 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/kr/pretty@v0.3.1 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/spf13/cobra — `github.com/spf13/cobra` is required at v1.5.0 in docs/cli-doc/REDACTED, but v1.10.2 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/spf13/cobra@v1.10.2 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/spf13/cobra — `github.com/spf13/cobra` is required at v1.5.0 in REDACTED, but v1.10.2 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/spf13/cobra@v1.10.2 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/spf13/cobra — `github.com/spf13/cobra` is required at v1.8.1 in REDACTED, but v1.10.2 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/spf13/cobra@v1.10.2 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/spf13/viper — `github.com/spf13/viper` is required at v1.11.0 in REDACTED, but v1.21.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/spf13/viper@v1.21.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/spf13/viper — `github.com/spf13/viper` is required at v1.11.0 in REDACTED, but v1.21.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/spf13/viper@v1.21.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/stretchr/testify — `github.com/stretchr/testify` is required at v1.8.0 in REDACTED, but v1.12.1 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/stretchr/testify@v1.12.1 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/thanhpk/randstr — `github.com/thanhpk/randstr` is required at v1.0.4 in REDACTED, but v1.0.7 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/thanhpk/randstr@v1.0.7 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/thanhpk/randstr — `github.com/thanhpk/randstr` is required at v1.0.4 in REDACTED, but v1.0.7 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/thanhpk/randstr@v1.0.7 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/txn2/txeh — `github.com/txn2/txeh` is required at v1.3.0 in REDACTED, but v1.8.1 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/txn2/txeh@v1.8.1 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/txn2/txeh — `github.com/txn2/txeh` is required at v1.3.0 in REDACTED, but v1.8.1 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/txn2/txeh@v1.8.1 && go mod tidy` and commit the updated REDACTED and go.sum.
+ 18 more in this group — see findings.md.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 2 file(s) — `frontend/control-center/src/pages/LLMConsumers/LLMConsumerItem/index.tsx`, `lib/typescript/httpclient/src/client.ts` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
Run 01a1e813-28e8-7bce-8e71-efad1a1ec042 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 263 · Warnings: 996 · Recommendations: 621 · Info: 43 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 17-11-2026 @ 05:55 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.