Public report of arthurcolle/agents.erl, published 30 October 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 report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey → Signed and filed in the standard's public register, 15 November 2026, 07:23 UTC · Survey ID cd_707e2bcde54b4a4f906ce6fa005454a8

arthurcolle/agents.erl

Measured 30 October 2026, 12:35 UTC, at code version 7d28d33

No regression since the last survey

A regression is a drop of 0.5 points or more in the score, or of 2.5 or more out of 10 in a dimension, since the last survey.

CAI score 32out of 100 Weak
CriticalWeakAdequateStrongExemplary
No change since the last survey

The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.

A large codebase: 166,488 lines of product code in 6 projects, tests not counted · Estimated rebuild effort: about 1.1 person-years · Weakest lens: Production Readiness, 21

Findings by how serious they are

71 critical 1119 serious 39 minor

18 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks 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

Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
30 October 2026, 12:35 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 Watchdog. It is open to any tool that implements it, and today Watchdog is the only one that does.

The score is deterministic, which means the same code always gets the same score. Watchdog works 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 ▸

78of 78 dimensions measured by tools.
1194of 1229 findings point to an exact file and line, so you can open each one in the code. The other 35 concern the repository as a whole, such as missing documentation.
78dimensions across 9 lenses, read from 166,488 lines of product code in 6 projects.
Chapters

Executive summary

arthurcolle/agents.erl falls short of our standard for a preview release because we found no working pipeline that builds or tests changes to the code and no automated security scanning of the code, its secrets or its dependencies. It scores 32 out of 100 and is rated Weak, and 18 of its 71 critical findings are security problems.

Production Readiness, at 21, is the weakest lens and counts most in the score. The best first step for the work it takes is fixing the project whose package versions aren't recorded, worth about 2 points. Adding an automated build and test pipeline would lift Production Readiness itself, worth about 3 points. Raising Production Readiness to 62 would lift the score to about 40.

Fifteen known security holes in the packages the code depends on can be used by attackers. Two passwords or keys are open to anyone who can read the repository, and twenty-six controls can't be used without a mouse. Updating the vulnerable packages, replacing each exposed password or key and making the controls work with a keyboard would close these risks. The place where the code runs text as code or as a command needs a direct call instead. The 11 labels or groups of fields with no name need connecting to their fields or naming.

The product code is 166,488 lines, about €160,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 for The 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.
Production Readiness 21 · counts for 45%Code Health 27 · counts for 25%Accessibility 32 · counts for 14%Event-Driven 61 · counts for 8%Security and Compliance 69 · counts for 4%Event Sourcing 74 · counts for 2%Maturity 82 · counts for 1%Architecture 93 · counts for 1%Performance 100 · counts for 0%

If Production Readiness rose from 21 to 62, the lowest score rated Strong, the score would rise from 32 to about 40.

Code composition: what the lines of code are
Product code 90%Tests 10%
New since the last survey: 46 findings

These 46 critical or serious findings weren't in the previous survey, on 16 October 2026.

Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.

Fixed since the last survey: 275 findings

These 275 critical or serious findings were in the previous survey, on 16 October 2026, and are gone from this one. The first 100 are listed here.

  • Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
  • Code Duplication · Duplicated block (12 lines × 2 locations) apps/agent_web/frontend/src/components/ApiKeyManager.tsx
  • Code Duplication · Duplicated block (12 lines × 2 locations) apps/agent_web/frontend/src/components/ComprehensiveMCPManager.tsx
  • Code Duplication · Duplicated block (12 lines × 2 locations) apps/agent_web/frontend/src/components/ComprehensiveMCPManager.tsx
  • Code Duplication · Duplicated block (12 lines × 2 locations) apps/agent_web/frontend/src/components/ComprehensiveMCPManager.tsx
  • Code Duplication · Duplicated block (12 lines × 3 locations) apps/agent_web/frontend/src/components/CrashMonitorDashboard.tsx
  • Code Duplication · Duplicated block with local edits (12 matched lines × 2 locations) apps/agent_web/frontend/src/components/FleetManagementDashboard.tsx
  • Code Duplication · Duplicated block (12 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (12 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (12 lines × 2 locations) apps/agent_web/frontend/src/components/MainLayoutWithSidebar.tsx
  • Code Duplication · Duplicated block (12 lines × 2 locations) apps/agent_web/frontend/src/components/ModelTypeEditor.tsx
  • Code Duplication · Duplicated block (12 lines × 2 locations) apps/agent_web/frontend/src/components/PipedreamConnectionManager.tsx
  • Code Duplication · Duplicated block with local edits (11 matched lines × 2 locations) apps/agent_web/frontend/src/App.tsx
  • Code Duplication · Duplicated block (11 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block with local edits (11 matched lines × 2 locations) apps/agent_web/frontend/src/components/ClaudeCLI.tsx
  • Code Duplication · Duplicated block (11 lines × 3 locations) apps/agent_web/frontend/src/components/CrashMonitorDashboard.tsx
  • Code Duplication · Duplicated block (11 lines × 2 locations) apps/agent_web/frontend/src/components/ErrorInterpretationPanel.tsx
  • Code Duplication · Duplicated block (11 lines × 2 locations) apps/agent_web/frontend/src/components/ErrorInterpretationPanel.tsx
  • Code Duplication · Duplicated block (11 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (11 lines × 2 locations) apps/agent_web/frontend/src/components/ModelConfiguration.tsx
  • Code Duplication · Duplicated block (11 lines × 2 locations) apps/agent_web/frontend/src/components/MonitoringPanel.tsx
  • Code Duplication · Duplicated block (11 lines × 2 locations) apps/agent_web/frontend/src/components/UltraAdvancedDashboard.tsx
  • Code Duplication · Duplicated block (10 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (10 lines × 4 locations) apps/agent_web/frontend/src/components/ChainOfThoughtVisualization.tsx
  • Code Duplication · Duplicated block with local edits (10 matched lines × 2 locations) apps/agent_web/frontend/src/components/CrashMonitorDashboard.tsx
  • Code Duplication · Duplicated block (10 lines × 3 locations) REDACTED
  • Code Duplication · Duplicated block (10 lines × 4 locations) apps/agent_web/frontend/src/components/DiscoveryMeshDashboard.tsx
  • Code Duplication · Duplicated block (10 lines × 8 locations) apps/agent_web/frontend/src/components/DiscoveryMeshDashboard.tsx
  • Code Duplication · Duplicated block (10 lines × 2 locations) apps/agent_web/frontend/src/components/FleetManagementDashboard.tsx
  • Code Duplication · Duplicated block (10 lines × 3 locations) apps/agent_web/frontend/src/components/MCPServerManager.tsx
  • Code Duplication · Duplicated block (10 lines × 2 locations) apps/agent_web/frontend/src/components/ModelConfiguration.tsx
  • Code Duplication · Duplicated block (10 lines × 2 locations) apps/agent_web/frontend/src/components/ModelTypeEditor.tsx
  • Code Duplication · Duplicated block (10 lines × 2 locations) apps/agent_web/frontend/src/components/MultiAgentChat.tsx
  • Code Duplication · Duplicated block (10 lines × 2 locations) apps/agent_web/frontend/src/components/QuantumConsciousnessInterface.tsx
  • Code Duplication · Duplicated block (10 lines × 3 locations) REDACTED
  • Code Duplication · Duplicated block (10 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (10 lines × 3 locations) apps/agent_web/frontend/src/components/UltraAdvancedDashboard.tsx
  • Code Duplication · Duplicated block (9 lines × 3 locations) apps/agent_web/frontend/src/components/CleanSystemDashboard.tsx
  • Code Duplication · Duplicated block (9 lines × 3 locations) apps/agent_web/frontend/src/components/CrashMonitorDashboard.tsx
  • Code Duplication · Duplicated block (9 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (9 lines × 2 locations) apps/agent_web/frontend/src/components/DiscoveryMeshDashboard.tsx
  • Code Duplication · Duplicated block (9 lines × 2 locations) apps/agent_web/frontend/src/components/DiscoveryMeshDashboard.tsx
  • Code Duplication · Duplicated block (9 lines × 2 locations) apps/agent_web/frontend/src/components/ErrorInterpretationPanel.tsx
  • Code Duplication · Duplicated block (9 lines × 3 locations) apps/agent_web/frontend/src/components/FleetManagementDashboard.tsx
  • Code Duplication · Duplicated block (9 lines × 2 locations) apps/agent_web/frontend/src/components/MCPServerManager.tsx
  • Code Duplication · Duplicated block (9 lines × 5 locations) apps/agent_web/frontend/src/components/MainLayoutWithSidebar.tsx
  • Code Duplication · Duplicated block (9 lines × 4 locations) apps/agent_web/frontend/src/components/MainLayoutWithSidebar.tsx
  • Code Duplication · Duplicated block (9 lines × 2 locations) apps/agent_web/frontend/src/components/MultiAgentChat.tsx
  • Code Duplication · Duplicated block (9 lines × 2 locations) apps/agent_web/frontend/src/components/SystemMonitoringDashboard.tsx
  • Code Duplication · Duplicated block (9 lines × 2 locations) apps/agent_web/frontend/src/components/UltimatePerformanceDashboard.tsx
  • Code Duplication · Duplicated block (9 lines × 2 locations) apps/agent_web/frontend/src/components/UltimatePerformanceDashboard.tsx
  • Code Duplication · Duplicated block (9 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (9 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (9 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (8 lines × 5 locations) apps/agent_web/frontend/src/components/AdaptiveAIInterface.tsx
  • Code Duplication · Duplicated block (8 lines × 2 locations) apps/agent_web/frontend/src/components/AdvancedStructuredOutputsManager.tsx
  • Code Duplication · Duplicated block (8 lines × 12 locations) apps/agent_web/frontend/src/components/AdvancedStructuredOutputsManager.tsx
  • Code Duplication · Duplicated block (8 lines × 2 locations) apps/agent_web/frontend/src/components/ChainOfThoughtVisualization.tsx
  • Code Duplication · Duplicated block (8 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (8 lines × 8 locations) apps/agent_web/frontend/src/components/DiscoveryMeshDashboard.tsx
  • Code Duplication · Duplicated block (8 lines × 2 locations) apps/agent_web/frontend/src/components/MCPOrchestrationEngine.tsx
  • Code Duplication · Duplicated block (8 lines × 2 locations) apps/agent_web/frontend/src/components/QuantumConsciousnessInterface.tsx
  • Code Duplication · Duplicated block (8 lines × 2 locations) apps/agent_web/frontend/src/components/SystemMonitoringDashboard.tsx
  • Code Duplication · Duplicated block (8 lines × 6 locations) apps/agent_web/frontend/src/components/ui/scroll-area.tsx
  • Code Duplication · Duplicated block (8 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (7 lines × 3 locations) REDACTED
  • Code Duplication · Duplicated block (7 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (7 lines × 2 locations) apps/agent_web/frontend/src/components/DiscoveryMeshDashboard.tsx
  • Code Duplication · Duplicated block (7 lines × 2 locations) apps/agent_web/frontend/src/components/FlameGraph.tsx
  • Code Duplication · Duplicated block (7 lines × 2 locations) apps/agent_web/frontend/src/components/FleetManagementDashboard.tsx
  • Code Duplication · Duplicated block (7 lines × 4 locations) apps/agent_web/frontend/src/components/UltraAdvancedDashboard.tsx
  • Code Duplication · Duplicated block (7 lines × 4 locations) apps/agent_web/frontend/src/components/ui/progress.tsx
  • Code Duplication · Duplicated block (7 lines × 3 locations) REDACTED
  • Code Duplication · Duplicated block (6 lines × 2 locations) apps/agent_web/frontend/src/components/ComprehensiveMCPManager.tsx
  • Code Duplication · Duplicated block (6 lines × 2 locations) apps/agent_web/frontend/src/components/MonitoringPanel.tsx
  • Code Duplication · Duplicated block (6 lines × 2 locations) apps/agent_web/frontend/src/components/SystemMonitoringDashboard.tsx
  • Code Duplication · Duplicated block (6 lines × 5 locations) REDACTED
  • Code Duplication · Duplicated block (5 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block with local edits (5 matched lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (5 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (5 lines × 2 locations) apps/agent_web/frontend/src/components/ErrorInterpretationPanel.tsx
  • Code Duplication · Duplicated block (5 lines × 2 locations) apps/agent_web/frontend/src/components/NetworkTopology.tsx
  • Handler temporal coupling · Handler temporal coupling: openai_files clause `handle_call/3#188` apps/openai/src/openai_files.erl
  • Handler temporal coupling · Handler temporal coupling: openai_responses clause `handle_call/3#130` apps/openai/src/openai_responses.erl
  • Handler temporal coupling · Handler temporal coupling: openai_responses clause `handle_call/3#155` apps/openai/src/openai_responses.erl
  • Handler temporal coupling · Handler temporal coupling: openai_responses clause `handle_call/3#163` apps/openai/src/openai_responses.erl
  • Handler temporal coupling · Handler temporal coupling: openai_responses clause `handle_call/3#171` apps/openai/src/openai_responses.erl
  • Handler temporal coupling · Handler temporal coupling: openai_responses clause `handle_call/3#179` apps/openai/src/openai_responses.erl
  • Handler temporal coupling · Handler temporal coupling: openapi_metrics clause `handle_call/3#151` apps/openapi_scaffold/src/openapi_metrics.erl
  • Handler temporal coupling · Handler temporal coupling: openapi_playground clause `handle_call/3#99` apps/openapi_scaffold/src/openapi_playground.erl
  • Handler temporal coupling · Handler temporal coupling: openapi_playground clause `handle_ws_message/2#665` apps/openapi_scaffold/src/openapi_playground.erl
  • Handler temporal coupling · Handler temporal coupling: openapi_proxy clause `handle_call/3#63` apps/openapi_scaffold/src/openapi_proxy.erl
  • Handler temporal coupling · Handler temporal coupling: openapi_time_travel clause `handle_call/3#131` apps/openapi_scaffold/src/openapi_time_travel.erl
  • Handler temporal coupling · Handler temporal coupling: agent clause `handle_follow_up/3#275` sandbox/myapp/apps/myapp/src/agent.erl
  • Handler temporal coupling · Handler temporal coupling: agent_messenger clause `handle_call/3#93` sandbox/myapp/apps/myapp/src/agent_messenger.erl
  • Cancellation propagation · Async function without AbortSignal: loadMcpServers apps/agent_web/frontend/src/components/ToolRegistry.tsx
  • Cancellation propagation · Async function without AbortSignal: loadTimelineEvents apps/agent_web/frontend/src/components/Timeline.tsx
  • Cancellation propagation · Async function without AbortSignal: fetchSystemData apps/agent_web/frontend/src/components/SystemMonitoringDashboard.tsx
  • Cancellation propagation · Async function without AbortSignal: fetchErrors apps/agent_web/frontend/src/components/SystemMonitoringDashboard.tsx
Rebuild cost: about €160,000 · Estimate
Cost to rebuild€52,000 to €260,000, for 869 to 2,758 hours of work, about 1.1 person-years for 1 to 3 engineers
Difficulty of the problemStandard, 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 32. 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.
SizeLarge: 166,488 lines of product code
What it is notNot 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: Watchdog prices 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 1 Dependency not covered by the lockfile finding(s) in Dependency Hygiene.
Raises the score by about 2 points · Low effort · Dependency Hygiene
2
Resolve the 1 Floating source dependency finding(s) in Dependency Hygiene.
Raises the score by about 2 points · Low effort · Dependency Hygiene
3
Add a CI workflow that builds and runs the test suite on every push/PR.
Raises the score by about 3 points · Medium effort · CI/CD gates

Diagnosis: what the measurements show together

Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.

Where the investment is most exposed · Value at risk
This code would cost about €160,000 to build again, about 1.1 person-years of work. Its weakest lens is Production Readiness, at 21 (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 1 Dependency not covered by the lockfile finding(s) in Dependency Hygiene. Of all the actions in this report, it raises the score most for the work it takes: about 2 points for low effort, because it clears the 1 Dependency Hygiene 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.

arch agent-orchestration-ui agent-orchestration-ui agent_web agent_web agents agents agent_web->agents openai openai agent_web->openai agents->openai openapi_scaffold openapi_scaffold

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.

311 modules, with 37 dependencies between them. Every module uses only modules listed above it, so there are no loops.

The table shows the 40 modules with the most connections; 271 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.
uses →1 (global)2 absolute_impossibility_orchestrator3 apps.agent_web.frontend.src.components.AdvancedMCPDashboard4 apps.agent_web.frontend.src.components.AdvancedMessageRenderer5 apps.agent_web.frontend.src.components.AgentCommunicationPanel6 apps.agent_web.frontend.src.components.AgentList7 apps.agent_web.frontend.src.components.AgentPillXL8 apps.agent_web.frontend.src.components.ApiKeyNotification9 apps.agent_web.frontend.src.components.ClaudeCLI10 apps.agent_web.frontend.src.components.CommandPalette11 apps.agent_web.frontend.src.components.ComprehensiveMCPManager12 apps.agent_web.frontend.src.components.ContextMenu13 apps.agent_web.frontend.src.components.CreateAgentDialog14 apps.agent_web.frontend.src.components.Dashboard15 apps.agent_web.frontend.src.components.DenseLayout16 apps.agent_web.frontend.src.components.ExamplesPanel17 apps.agent_web.frontend.src.components.FlameGraph18 apps.agent_web.frontend.src.components.InteractiveWidgets19 apps.agent_web.frontend.src.components.MainLayoutWithSidebar20 apps.agent_web.frontend.src.components.MonitoringPanel21 apps.agent_web.frontend.src.components.MultiAgentChat22 apps.agent_web.frontend.src.components.NetworkTopology23 apps.agent_web.frontend.src.components.OpStackBar24 apps.agent_web.frontend.src.components.RightDrawerInspector25 apps.agent_web.frontend.src.components.SimpleAdvancedChat26 apps.agent_web.frontend.src.components.Timeline27 apps.agent_web.frontend.src.components.TokenHeatmap28 apps.agent_web.frontend.src.components.VirtualizedAgentList29 apps.agent_web.frontend.src.components.ui.badge30 apps.agent_web.frontend.src.components.ui.command31 apps.agent_web.frontend.src.services.ChainOfThoughtEngine32 apps.agent_web.frontend.src.services.ContextualRetrieval33 apps.agent_web.frontend.src.components.AdvancedStructuredOutputsManager34 apps.agent_web.frontend.src.components.ChainOfThoughtVisualization35 apps.agent_web.frontend.src.components.CleanSystemDashboard36 apps.agent_web.frontend.src.components.DynamicUIManager37 apps.agent_web.frontend.src.components.InteractiveReasoningControls38 apps.agent_web.frontend.src.components.ResourceSentinelBar39 apps.agent_web.frontend.src.components.ui40 apps.agent_web.frontend.src.components
1 (global)
2 absolute_impossibility_orchestrator
3 apps.agent_web.frontend.src.components.AdvancedMCPDashboard
4 apps.agent_web.frontend.src.components.AdvancedMessageRenderer
5 apps.agent_web.frontend.src.components.AgentCommunicationPanel
6 apps.agent_web.frontend.src.components.AgentList
7 apps.agent_web.frontend.src.components.AgentPillXL
8 apps.agent_web.frontend.src.components.ApiKeyNotification
9 apps.agent_web.frontend.src.components.ClaudeCLI
10 apps.agent_web.frontend.src.components.CommandPalette
11 apps.agent_web.frontend.src.components.ComprehensiveMCPManager
12 apps.agent_web.frontend.src.components.ContextMenu
13 apps.agent_web.frontend.src.components.CreateAgentDialog
14 apps.agent_web.frontend.src.components.Dashboard
15 apps.agent_web.frontend.src.components.DenseLayout
16 apps.agent_web.frontend.src.components.ExamplesPanel
17 apps.agent_web.frontend.src.components.FlameGraph
18 apps.agent_web.frontend.src.components.InteractiveWidgets
19 apps.agent_web.frontend.src.components.MainLayoutWithSidebar
20 apps.agent_web.frontend.src.components.MonitoringPanel
21 apps.agent_web.frontend.src.components.MultiAgentChat
22 apps.agent_web.frontend.src.components.NetworkTopology
23 apps.agent_web.frontend.src.components.OpStackBar
24 apps.agent_web.frontend.src.components.RightDrawerInspector
25 apps.agent_web.frontend.src.components.SimpleAdvancedChat
26 apps.agent_web.frontend.src.components.Timeline
27 apps.agent_web.frontend.src.components.TokenHeatmap
28 apps.agent_web.frontend.src.components.VirtualizedAgentList
29 apps.agent_web.frontend.src.components.ui.badge
30 apps.agent_web.frontend.src.components.ui.command
31 apps.agent_web.frontend.src.services.ChainOfThoughtEngine
32 apps.agent_web.frontend.src.services.ContextualRetrieval
33 apps.agent_web.frontend.src.components.AdvancedStructuredOutputsManager1
34 apps.agent_web.frontend.src.components.ChainOfThoughtVisualization1
35 apps.agent_web.frontend.src.components.CleanSystemDashboard1
36 apps.agent_web.frontend.src.components.DynamicUIManager1
37 apps.agent_web.frontend.src.components.InteractiveReasoningControls1
38 apps.agent_web.frontend.src.components.ResourceSentinelBar1
39 apps.agent_web.frontend.src.components.ui11
40 apps.agent_web.frontend.src.components11111113112111111111121111111
Uses a module listed above itPart of a loopThe module itself
1 (global)2 absolute_impossibility_orchestrator3 apps.agent_web.frontend.src.components.AdvancedMCPDashboard4 apps.agent_web.frontend.src.components.AdvancedMessageRenderer5 apps.agent_web.frontend.src.components.AgentCommunicationPanel6 apps.agent_web.frontend.src.components.AgentList7 apps.agent_web.frontend.src.components.AgentPillXL8 apps.agent_web.frontend.src.components.ApiKeyNotification9 apps.agent_web.frontend.src.components.ClaudeCLI10 apps.agent_web.frontend.src.components.CommandPalette11 apps.agent_web.frontend.src.components.ComprehensiveMCPManager12 apps.agent_web.frontend.src.components.ContextMenu13 apps.agent_web.frontend.src.components.CreateAgentDialog14 apps.agent_web.frontend.src.components.Dashboard15 apps.agent_web.frontend.src.components.DenseLayout16 apps.agent_web.frontend.src.components.ExamplesPanel17 apps.agent_web.frontend.src.components.FlameGraph18 apps.agent_web.frontend.src.components.InteractiveWidgets19 apps.agent_web.frontend.src.components.MainLayoutWithSidebar20 apps.agent_web.frontend.src.components.MonitoringPanel21 apps.agent_web.frontend.src.components.MultiAgentChat22 apps.agent_web.frontend.src.components.NetworkTopology23 apps.agent_web.frontend.src.components.OpStackBar24 apps.agent_web.frontend.src.components.RightDrawerInspector25 apps.agent_web.frontend.src.components.SimpleAdvancedChat26 apps.agent_web.frontend.src.components.Timeline27 apps.agent_web.frontend.src.components.TokenHeatmap28 apps.agent_web.frontend.src.components.VirtualizedAgentList29 apps.agent_web.frontend.src.components.ui.badge30 apps.agent_web.frontend.src.components.ui.command31 apps.agent_web.frontend.src.services.ChainOfThoughtEngine32 apps.agent_web.frontend.src.services.ContextualRetrieval33 apps.agent_web.frontend.src.components.AdvancedStructuredOutputsManager34 apps.agent_web.frontend.src.components.ChainOfThoughtVisualization35 apps.agent_web.frontend.src.components.CleanSystemDashboard36 apps.agent_web.frontend.src.components.DynamicUIManager37 apps.agent_web.frontend.src.components.InteractiveReasoningControls38 apps.agent_web.frontend.src.components.ResourceSentinelBar39 apps.agent_web.frontend.src.components.ui40 apps.agent_web.frontend.src.components(global)1absolute_impossibility_orchestrator2apps.agent_web.frontend.src.components.AdvancedMCPDashboard3apps.agent_web.frontend.src.components.AdvancedMessageRenderer4apps.agent_web.frontend.src.components.AgentCommunicationPanel5apps.agent_web.frontend.src.components.AgentList6apps.agent_web.frontend.src.components.AgentPillXL7apps.agent_web.frontend.src.components.ApiKeyNotification8apps.agent_web.frontend.src.components.ClaudeCLI9apps.agent_web.frontend.src.components.CommandPalette10apps.agent_web.frontend.src.components.ComprehensiveMCPManager11apps.agent_web.frontend.src.components.ContextMenu12apps.agent_web.frontend.src.components.CreateAgentDialog13apps.agent_web.frontend.src.components.Dashboard14apps.agent_web.frontend.src.components.DenseLayout15apps.agent_web.frontend.src.components.ExamplesPanel16apps.agent_web.frontend.src.components.FlameGraph17apps.agent_web.frontend.src.components.InteractiveWidgets18apps.agent_web.frontend.src.components.MainLayoutWithSidebar19apps.agent_web.frontend.src.components.MonitoringPanel20apps.agent_web.frontend.src.components.MultiAgentChat21apps.agent_web.frontend.src.components.NetworkTopology22apps.agent_web.frontend.src.components.OpStackBar23apps.agent_web.frontend.src.components.RightDrawerInspector24apps.agent_web.frontend.src.components.SimpleAdvancedChat25apps.agent_web.frontend.src.components.Timeline26apps.agent_web.frontend.src.components.TokenHeatmap27apps.agent_web.frontend.src.components.VirtualizedAgentList28apps.agent_web.frontend.src.components.ui.badge29apps.agent_web.frontend.src.components.ui.command30apps.agent_web.frontend.src.services.ChainOfThoughtEngine31apps.agent_web.frontend.src.services.ContextualRetrieval32apps.agent_web.frontend.src.components.AdvancedStructuredOutputsManager33apps.agent_web.frontend.src.components.ChainOfThoughtVisualization34apps.agent_web.frontend.src.components.CleanSystemDashboard35apps.agent_web.frontend.src.components.DynamicUIManager36apps.agent_web.frontend.src.components.InteractiveReasoningControls37apps.agent_web.frontend.src.components.ResourceSentinelBar38apps.agent_web.frontend.src.components.ui39apps.agent_web.frontend.src.components401111111111111113112111111111121111111+271 more modules (most-connected shown)

At a glance — Code Health · 27% · Weak · gated by D3, R3, R7, X5 ·

At a glance — Architecture · 93% · Adequate · gated by D26 ·

At a glance — Maturity · 82% · Strong ·

At a glance — Readiness · 21% · Weak · gated by R4, R8, P1, P3, P7 ·

At a glance — Security · 69% · Adequate · gated by D30 ·

At a glance — Event-Driven · 61% · Adequate ·

At a glance — Event Sourcing · 74% · Strong ·

At a glance — Accessibility · 32% · Weak · gated by AC1, AC2, AC4 ·

At a glance — Performance · 100% · Exemplary ·

Security & Compliance — OWASP Top-10 mapping

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 categoryFindingsSeverity
A03:2025 — Software Supply Chain Failures21High / Critical
A05:2025 — Injection7High / Critical
A07:2025 — Authentication Failures3High / Critical

Roadmap

Top priorities: Add a CI workflow that builds and runs the test suite on every push/PR; Run what this repository's stack ships: dialyzer or elvis — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing; Add tests that import the unreached modules (directly or through their public entry).

Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.

Do thisHelpsEffortDimension
Resolve the 1 Dependency not covered by the lockfile finding(s) in Dependency Hygiene.+2.4 ptsLowDependency Hygiene
Resolve the 1 Floating source dependency finding(s) in Dependency Hygiene.+2.4 ptsLowDependency Hygiene
Add a CI workflow that builds and runs the test suite on every push/PR.+3.3 ptsMediumCI/CD gates
Run what this repository's stack ships: dialyzer or elvis — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.+3.3 ptsMediumSecurity & performance tooling
Add tests that import the unreached modules (directly or through their public entry).+3.3 ptsMediumTest Coverage
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.+1.9 ptsMediumLarge Files
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.+1.9 ptsMediumDead Code
Pass an explicit bound on every request — `{timeout, Ms}` in `httpc:request/4`'s HTTP options (its default is `infinity`), `{recv_timeout, Ms}` for hackney, a timeout on `gun:await/3` — and wrap dependencies that fail in a breaker (`fuse`) with back-off (`backoff`).+1.6 ptsMediumOutbound HTTP resilience

File quality

Per-file score 0–10 — a quality signature. Of 304 files carrying findings, judged against the Preview bar: 0% slop · 4% mixed · 96% near-clean.

FileScoreBandWorst signal
REDACTED0.0SlopDependency Vulnerabilities: High CVE: REDACTED
REDACTED4.2MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.8MixedDependency Vulnerabilities: High CVE: REDACTED
REDACTED4.9MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.3MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.7MixedStatic Analysis (SAST): Medium: REDACTED
apps/openapi_scaffold/src/openapi_validator.erl6.0MixedExplicit Debt: TodoComment
apps/agent_web/src/crash_report_api_handler.erl6.0MixedExplicit Debt: TodoComment
apps/agents/src/mcp_server_config.erl6.0MixedExplicit Debt: TodoComment
apps/agents/src/agent_instance.erl6.0MixedExplicit Debt: TodoComment
apps/agents/src/dynamic_agent_router.erl6.0MixedExplicit Debt: TodoComment
REDACTED6.4MixedStatic Analysis (SAST): Medium: REDACTED
apps/agent_web/frontend/src/components/MonitoringPanel.tsx6.7MixedExplicit Debt: TodoComment
apps/agents/src/agent_tools.erl7.0Near-cleanCyclomatic Complexity: agent_tools.predefined_executor (cyclomatic 85)
apps/openai/src/openai_chat.erl7.0Near-cleanCyclomatic Complexity: openai_chat.do_create_chat_completion (cyclomatic 25)
apps/agents/src/agent_discovery.erl7.0Near-cleanCyclomatic Complexity: agent_discovery.handle_call (cyclomatic 24)
apps/agent_web/src/mcp_server.erl7.0Near-cleanCyclomatic Complexity: mcp_server.handle_mcp_request (cyclomatic 20)
apps/agent_web/src/consciousness_bridge_api_handler.erl7.0Near-cleanCyclomatic Complexity: consciousness_bridge_api_handler.handle_post (cyclomatic 19)
apps/agent_web/src/mcp_client_v2.erl7.0Near-cleanCyclomatic Complexity: mcp_client_v2.start_websocket_connection (cyclomatic 19)
apps/agents/src/jina_tools.erl7.0Near-cleanCognitive Complexity: jina_tools.jina_classify (cognitive 20)

How the grades work

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 — 71

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 — 1119

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 — 39

Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.

Could not be resolved — 18

Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.

Methodology & how to trust this report

Watchdog 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. 78 of 78 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.

Every figure here is one of three 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; ◐ Advisory — an LLM prose judgement. 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; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.

What we checked — 78 dimensions across the health lenses
D1D2D3D4D5D6D12D13D14D15D17D19D20D26D28D29D30D35D43AC1AC2AC3AC4AC5AC6AC7AX10AX3AX4AX9ED1ED2ES1ES2M1M2M3M4P1P10P2P3P6P7PF3R1R10R2R3R4R5R6R7R8R9S1X1X12X13X14X15X16X17X18X19X2X21X22X23X24X25X26X27X28X29X3X30X5

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
  1. 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, 1194 of 1229 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.)
  2. Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
  3. 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.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Watchdog duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivySecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3✓ deterministic
LLM (sampled · advisory)Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement—◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a18cce-7bd4-705a-833b-a31275c67da4.

The exact command behind every deep-scan dimension — tool, version, invocation and retained raw output — is in Appendix B — Reproduction & audit trail.

Run transparency — what happened this run

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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.erl) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (`rebar3 do eunit --cover, cover` (or covertool for Cobertura XML)) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (`rebar3 do eunit --cover, cover` (or covertool for Cobertura XML)) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
  • D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.erl) and this repository declares a rebar3 project (repository root, 12 test files), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
  • D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 31 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
  • D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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 — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
  • D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
  • D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: it declares a published package (apps/openapi_scaffold/src/openapi_scaffold.app.src), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
  • D24 Comment Value — not measured this run — Watchdog 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.
  • D27 Navigability — not measured this run — Watchdog 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. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
  • D34 Knowledge Freshness — 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. Too few commits to judge knowledge freshness (31 commit(s) sampled).
  • D44 Platform End-of-Life — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
  • AC2 Forms & labels — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. 58 further occurrence(s) are not listed individually; the score already reflects all 98.
  • AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (dev). the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence.
  • C1 Data Protection — not measured this run — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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.
  • ED1 Handler temporal coupling — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. 13 further occurrence(s) are not listed individually; the score already reflects all 53.
  • GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Erlang, Python is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Erlang, Python is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
  • P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
  • R10 Code Duplication — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. 81 further occurrence(s) are not listed individually; the score already reflects all 121.
  • X2 Cancellation propagation — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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.
  • X24 Document value interpolated into markup unescaped — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. 10 further occurrence(s) are not listed individually; the score already reflects all 50.
  • X3 Exception handling — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. 108 further occurrence(s) are not listed individually; the score already reflects all 148.
  • X4 Structured logging — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X7 Silent fallback defaults — not measured this run — Watchdog 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. X7 measured the part of this repository it reads (C#, Python, TypeScript/JavaScript, Rust, Go, Java, Kotlin, Scala, PHP, Ruby, Swift and Dart), and its Erlang source is outside the check's reach, so the card covers only part of the product. That is a gap in this analyzer's language reach — not a finding that the unread source is free of silent defaults.

Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.

Limitations & what we did not check

Watchdog assesses the repository exactly as committed, and only the repository. By design it does 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.
  • 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 is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
  • 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.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
  • AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
  • AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
  • AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
  • AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
  • AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
  • AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
  • M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
  • 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.

Dimensions

D1 · Cyclomatic Complexity5.9 / 10Adequate✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 5.9 / 10 · rule-coverage 100% · ceiling Prevented

90 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was AdvancedMCPDashboard.AdvancedMCPDashboard at 113. A further 34 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 swagger_docs_handler.get_endpoint_info at 29 — they are counted neither in the figure above nor in this dimension's score. 29 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: apps/agent_web/src/swagger_docs_handler.erl (swagger_docs_handler.get_endpoint_info at 29), apps/agents/src/agent_instance.erl (agent_instance.handle_call at 29), apps/agent_web/src/colored_logger.erl (colored_logger.apply_color at 28), apps/agents/src/specialized_agent_templates.erl (specialized_agent_templates.get_specialized_tools at 22), apps/agents/src/agent_scheduler_engine.erl (agent_scheduler_engine.handle_call at 21), and 24 more not listed here. 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.

AdvancedMCPDashboard.AdvancedMCPDashboard (cyclomatic 113)REDACTED:157
SimpleAdvancedChat.SimpleAdvancedChat (cyclomatic 104)REDACTED:384
agent_tools.predefined_executor (cyclomatic 85)apps/agents/src/agent_tools.erl:1319
hyper_graph_storage.handle_call (cyclomatic 73)apps/agent_web/src/hyper_graph_storage.erl:125
embedding_integration.handle_call (cyclomatic 70)apps/agent_web/src/embedding_integration.erl:86

+ 85 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Bring the 8 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with AdvancedMCPDashboard.AdvancedMCPDashboard (cyclomatic 113), SimpleAdvancedChat.SimpleAdvancedChat (cyclomatic 104), agent_tools.predefined_executor (cyclomatic 85). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 8 together lifts Cyclomatic Complexity from 5.9 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
  2. Stand up a CI pipeline, then gate Cyclomatic Complexity in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.

D2 · Cognitive Complexity6.0 / 10Adequate✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 6.0 / 10 · rule-coverage 100% · ceiling Prevented

87 method(s) exceeded the cognitive complexity threshold of 15; the worst was SimpleAdvancedChat.SimpleAdvancedChat at 100.

SimpleAdvancedChat.SimpleAdvancedChat (cognitive 100)REDACTED:384
colored_io.detect_log_type (cognitive 90)apps/agent_web/src/colored_io.erl:54
AdvancedMCPDashboard.AdvancedMCPDashboard (cognitive 89)REDACTED:157
AdvancedMessageRenderer.AdvancedMessageRenderer (cognitive 62)apps/agent_web/frontend/src/components/AdvancedMessageRenderer.tsx:22
CrashMonitorDashboard.CrashMonitorDashboard (cognitive 56)apps/agent_web/frontend/src/components/CrashMonitorDashboard.tsx:86

+ 82 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Bring the 4 bodies over 60 down to 60 or less in Cognitive Complexity — start with SimpleAdvancedChat.SimpleAdvancedChat (cognitive 100), colored_io.detect_log_type (cognitive 90), AdvancedMCPDashboard.AdvancedMCPDashboard (cognitive 89). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cognitive Complexity from 6.0 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
  2. Stand up a CI pipeline, then gate Cognitive Complexity in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.

D3 · God Classes3.9 / 10Weak✓ 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.

Maturity: Documented → Verified → Prevented · effective 3.9 / 10 · rule-coverage 100% · ceiling Prevented

239 god class(es) detected.

TooManyFunctions: distributed_consciousness_engine · ×94apps/agents/src/distributed_consciousness_engine.erl:12
FileTooLong: src/agent_tools.erl · ×74apps/agents/src/agent_tools.erl
FunctionTooLong: AdvancedMCPDashboard.AdvancedMCPDashboard · ×56REDACTED:157
ClassTooLong: AdvancedMCPDashboard · ×13REDACTED:1
TooManyMethods: ChainOfThoughtEngine · ×2apps/agent_web/frontend/src/services/ChainOfThoughtEngine.ts:74

What to do

  1. Resolve the 94 TooManyFunctions finding(s) in God Classes — start with distributed_consciousness_engine.erl, quantum_runtime.erl, time_travel_debugging.erl. — One of this dimension's main actionable groups (94 warning-level).
  2. Resolve the 74 FileTooLong finding(s) in God Classes — start with agent_tools.erl, agent_instance.erl, REDACTED. — One of this dimension's main actionable groups (74 warning-level).
  3. Resolve the 56 FunctionTooLong finding(s) in God Classes — start with REDACTED (3), REDACTED (2), ComprehensiveMCPManager.tsx (2). — One of this dimension's main actionable groups (56 warning-level).
  4. Stand up a CI pipeline, then gate God Classes in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.

D4 · Code Duplication9.1 / 10Stronggated by 318 serious findings✓ Tool-verified

What it measures: Copy-pasted code that should be shared instead.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.

Maturity: Documented → Verified → Prevented · effective 9.1 / 10 · rule-coverage 100% · ceiling Verified

300 duplicated block group(s) detected. A further 18 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 1 of the 318 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.

Duplicated block (5 lines × 2) · ×35apps/agent_web/src/consciousness_bridge_api_handler.erl:60
Duplicated block (6 lines × 2) · ×24apps/agent_web/src/claude_config_handler.erl:23
Duplicated block (9 lines × 2) · ×22apps/agent_web/src/consciousness_bridge_api_handler.erl:234
Duplicated block (7 lines × 2) · ×21apps/agent_web/src/agent_scheduling_handler.erl:49
Duplicated block (8 lines × 2) · ×20apps/agent_web/src/colored_logger_handler.erl:156

+ 93 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 35 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with consciousness_bridge_api_handler.erl (3), jina_tools.erl (3), model_definition_manager.erl (2). — One of this dimension's main actionable groups (35 warning-level).
  2. Resolve the 24 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with mcp_api_handler.erl (2), agent_instance.erl (2), embedding_integration.erl (2). — One of this dimension's main actionable groups (24 warning-level).
  3. Resolve the 22 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with embedding_integration.erl (2), openapi_graphql_bridge.erl (2), consciousness_bridge_api_handler.erl. — One of this dimension's main actionable groups (22 warning-level).
  4. Stand up a CI pipeline, then gate Code Duplication in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.

D5 · Coupling8.4 / 10Strong✓ 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.

Maturity: Documented → Verified → Prevented · effective 8.4 / 10 · rule-coverage 100% · ceiling Prevented

5 production modules (npm+OTP), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence.

Off the main sequence: openai

What to do

  1. Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
  2. Stand up a CI pipeline, then gate Coupling in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.

D6 · Cohesion (LCOM4)9.9 / 10Stronggated by 1 serious finding✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.9 / 10 · rule-coverage 100% · ceiling Verified

1 of 211 classes have LCOM4 above 3.

Low cohesion: hierarchical_task_executor (LCOM4 4)apps/agents/src/hierarchical_task_executor.erl:4

What to do

  1. Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with hierarchical_task_executor.erl. — One of this dimension's main actionable groups (1 warning-level).
  2. Stand up a CI pipeline, then gate Cohesion (LCOM4) in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.

D12 · Dependency Hygiene8.8 7.6 / 10Strong✓ Tool-verified

What it measures: Whether dependencies are current, secure, and not bloated.

Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.

Maturity: Documented → Verified → Prevented · effective 7.6 / 10 · rule-coverage 86% · ceiling Verified

15 outdated, 0 retired direct Hex dependencies declared by rebar3, 2 pinning defect(s). 19 of 22 Hex declarations were graded against hex.pm (0 not published there, 3 not resolved to a release by a committed `REDACTED`). A dependency declared at an EXACT version — rebar3's own idiom — is graded against the current release and its remedy is an edit to the `rebar.config` declaration, because `rebar3 upgrade` cannot move past the version the manifest names; a `~>` or bounded requirement that EXCLUDES the newest release is reported as nothing, because that bound is a deliberate constraint. A `{ref, …}`, `{tag, …}` or branch-tracked git dependency is not graded for currency at all: its version is a revision, not a Hex release. Whether any of these packages is UNMAINTAINED is not graded — hex.pm publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: a large idiomatic class of BEAM dependencies — runtime adapters, codec plugins, protocol implementations and OTP applications the release starts — is correctly declared and never referenced in source. Known CVEs in this dependency graph are D30's question.

Floating source dependency: jesse
Dependency not covered by the lockfile: jsx
Outdated: accept · ×15

What to do

  1. Resolve the 1 Floating source dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 Dependency not covered by the lockfile finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
  3. Stand up a CI pipeline, then gate Dependency Hygiene in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.

D13 · REDACTED Scanning10.0 / 10Exemplary○ Nothing flagged

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

REDACTED scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

D14 · License Compliance10.0 / 10Exemplary○ Nothing flagged

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 33 shipped Hex package(s) use a banned license. Licences were resolved from hex.pm over the packages a consumer installs — this repository's REDACTED, which is already the transitive closure a consumer installs. rebar3 writes that lock for the DEFAULT profile ONLY, so a dependency declared inside `{profiles, [{test, [{deps, […]}]}]}` has no entry in it and is excluded here for the reason the Mix arm excludes an `only: [:dev, :test]` declaration: it is not installed by anything that depends on this repository. Each licence is the one hex.pm publishes for the package's current release. A further 1 package(s) the closure reaches resolve from git, a path or a local override and publish no licence this pass can read; they are outside this verdict. This repository publishes itself under MIT / Apache 2.0 / Apache-2.0, which is its own choice and is not judged here.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots10.0 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No churn × complexity hotspots in the window.

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md.

D17 · Explicit Debt10.0 / 10Stronggated by 14 serious findings✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

14 deducted task-comment markers across 166488 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.

TodoComment · ×14apps/openapi_scaffold/src/openapi_parser.erl:222

What to do

  1. Resolve the 14 TodoComment finding(s) in Explicit Debt — start with dynamic_agent_router.erl (2), crash_report_api_handler.erl (2), timeline_ws_handler.erl (2). — One of this dimension's main actionable groups (14 warning-level).
  2. Stand up a CI pipeline, then gate Explicit Debt in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.

D19 · Documentation Quality10.0 / 10Exemplary○ Nothing flagged

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

1 of 1 documentation facets pass in full. 52 document(s) read across 1 unit(s).

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

D20 · ADR Quality0.0 / 10Critical✓ Tool-verified

What it measures: Whether architecture decisions are recorded well (context, decision, consequences).

Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

No architecture decision records were found.

No ADRs found

What to do

  1. Resolve the 1 No ADRs found finding(s) in ADR Quality. — 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.

D26 · Project Cohesion3.3 / 10Weak✓ Tool-verified

What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.

Method: Project size overshoot penalties (LoC / public-type count / namespace count, 2-of-3 flag) weighted by log magnitude. Exhaustive across projects, deterministic, LLM-independent.

Maturity: Documented → Verified → Prevented · effective 3.3 / 10 · rule-coverage 100% · ceiling Documented

2 of 6 build units (OTP, npm, rebar3) flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesion

What to do

  1. Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.

D28 · Secrets (history)8.0 / 10Adequategated by 2 critical findings✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 8.0 / 10 · rule-coverage 100% · ceiling Documented

2 finding(s): 0 critical, 2 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.

REDACTED
REDACTED

What to do

  1. Resolve the 2 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
  2. 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.

D29 · Static Analysis (SAST)6.2 / 10Adequate✓ Tool-verified

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).

Maturity: Documented → Verified → Prevented · effective 6.2 / 10 · rule-coverage 100% · ceiling Documented

7 finding(s): 0 critical, 1 high, 6 medium, 0 low. semgrep hit a parse error in 11 file(s) — `apps/agents/doc/agent_discovery.html` (lines 311–313, lines 344–347, lines 376–378, …), `apps/agents/doc/agent_messenger.html` (lines 337–339, lines 370–372, lines 404–406, …), `apps/agents/doc/agent_protocol.html` (lines 275–276, lines 304–306, lines 337–339, …), `apps/agents/doc/hello_world.html` (line 159, line 187), `apps/agents/doc/simple_agent.html` (line 209, line 237, line 265, …), … (+6 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

What to do

  1. Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (6 warning-level).
  2. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).

Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.

D30 · Dependency Vulnerabilities0.0 / 10Critical✓ Tool-verified

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 `REDACTED` 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.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

21 finding(s): 0 critical, 15 high, 4 medium, 2 low.

REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 15 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (11), REDACTED (4). — One of this dimension's main actionable groups (15 issue-level).
  2. Resolve the 3 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
  3. Resolve the 1 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.

D35 · Change Coupling10.0 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

D43 · Malicious Dependencies10.0 / 10Exemplary✓ Tool-verified

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. Scored 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. SCORED, not informational.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No dependency in any ecosystem this repository declares is published as malicious.

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

Frontend & cross-cutting dimensions

R = React/JS · M = Maturity · P = Readiness.

AC1 · Text alternatives2.4 / 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.

  • 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. (×5) — apps/agent_web/frontend/src/components/ChainOfThoughtVisualization.tsx:331, apps/agent_web/frontend/src/components/QuantumConsciousnessInterface.tsx:371, apps/agent_web/frontend/src/components/UltraAdvancedDashboard.tsx:276, …

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.
AC2 · Forms & labels3.1 / 10Weak✓ Tool-verified

Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.

Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×7) — REDACTED:555, REDACTED:1018, REDACTED:1030, …
  • This select is named only by the placeholder of its value part. Nothing is typed into a select, so the placeholder does not vanish on input: it is shown as the trigger's text until a value is chosen, and then the chosen value replaces it — so at no point does the control state what the choice is for, and the trigger's role (combobox) takes its name from the author, not from that text. Name it: an aria-label on the trigger, or an id on the trigger with a <label htmlFor> pointing at it. (×8) — apps/agent_web/frontend/src/components/AdvancedStructuredOutputsManager.tsx:351, apps/agent_web/frontend/src/components/AgentCommunicationPanel.tsx:150, apps/agent_web/frontend/src/components/AgentCommunicationPanel.tsx:164, …
  • 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). (×3) — apps/agent_web/frontend/src/components/AgentQuorumPanel.tsx:303, apps/agent_web/frontend/src/components/AgentQuorumPanel.tsx:309, apps/agent_web/frontend/src/components/ApiKeyNotification.tsx:96
  • 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. — apps/agent_web/frontend/src/components/ChainOfThoughtVisualization.tsx:331
  • 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. — apps/agent_web/frontend/src/components/ContextMenu.tsx:110
  • This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id alone, wherever it is set, names nothing until a label points at it). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. (×3) — apps/agent_web/frontend/src/components/CreateAgentDialog.tsx:64, apps/agent_web/frontend/src/components/DiscoveryMeshDashboard.tsx:408, apps/agent_web/frontend/src/components/FleetManagementDashboard.tsx:346
  • 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. (×6) — apps/agent_web/frontend/src/components/ErrorInterpretationPanel.tsx:288, apps/agent_web/frontend/src/components/FleetManagementDashboard.tsx:380, apps/agent_web/frontend/src/components/FleetManagementDashboard.tsx:408, …
  • This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. (×11) — apps/agent_web/frontend/src/components/FleetManagementDashboard.tsx:334, apps/agent_web/frontend/src/components/FleetManagementDashboard.tsx:345, apps/agent_web/frontend/src/components/InteractiveReasoningControls.tsx:240, …

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.
AC3 · Page structure6.7 / 10Strong✓ Tool-verified

Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.

Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. (×6) — REDACTED:1421, apps/agent_web/frontend/src/components/CrashMonitorDashboard.tsx:488, apps/agent_web/frontend/src/components/DiscoveryMeshDashboard.tsx:359, …

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.
AC4 · Keyboard semantics1.0 / 10Critical✓ Tool-verified

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. (×14) — REDACTED:571, apps/agent_web/frontend/src/components/AgentList.tsx:25, apps/agent_web/frontend/src/components/AgentPillXL.tsx:95, …
  • A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}. (×4) — apps/agent_web/frontend/src/components/DiscoveryMeshDashboard.tsx:288, apps/agent_web/frontend/src/components/InteractiveWidgets.tsx:150, apps/agent_web/frontend/src/components/InteractiveWidgets.tsx:180, …
  • This <div> 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. — apps/agent_web/frontend/src/components/OpStackBar.tsx:81
  • The repo's own CSS styles .agent-item with `cursor: pointer`, so this <li> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler. — REDACTED:496
  • A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. — REDACTED:501
  • The repo's own CSS styles .node with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler. (×5) — REDACTED:1331, REDACTED:1332, REDACTED:1333, …

What to do

  • Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness10.0 / 10Exemplary○ Nothing flagged

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.

AC6 · Visual & motion safety4.3 / 10Weak✓ Tool-verified

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.

  • <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. (×2) — apps/agent_web/frontend/src/components/AdvancedStructuredOutputsManager.tsx:421, apps/agent_web/frontend/src/components/ClaudeCLI.tsx:250
  • This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade. (×5) — apps/agent_web/frontend/src/components/DynamicUIManager.tsx:506, apps/agent_web/frontend/src/components/DynamicUIManager.tsx:548, apps/agent_web/frontend/src/components/MCPServerManager.tsx:196, …
  • <div> moves — its `animate-ping` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. — apps/agent_web/frontend/src/components/MCPOrchestrationEngine.tsx:454
  • <div> moves — its `animate-bounce` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. (×3) — REDACTED:1102, REDACTED:1103, REDACTED:1104
  • <div> moves — its inline style sets `animation: fadeInUp 0.3s ease-out` — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. — REDACTED:1251
  • `.agent-item.active` sets color: white on background-color: #6366f1 — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — apps/agent_web/priv/static/css/style.css:186
  • `.btn-primary` sets color: white on background-color: #6366f1 — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — apps/agent_web/priv/static/css/style.css:296
  • `.btn-success` sets color: white on background-color: #10b981 — 2.5:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — apps/agent_web/priv/static/css/style.css:305
  • `.btn-danger` sets color: white on background-color: #ef4444 — 3.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — apps/agent_web/priv/static/css/style.css:314
  • `.node` sets color: white on background-color: #3498db — 3.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — apps/agent_web/priv/static/css/style.css:785
  • `.header::before` moves (`animation: shimmer 20s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — apps/agent_web/priv/static/css/style.css:86
  • `.agent-item::before` moves (`transition: transform 0.6s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — apps/agent_web/priv/static/css/style.css:172
  • `.btn::before` moves (`transition: width 0.6s, height 0.6s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — apps/agent_web/priv/static/css/style.css:283
  • `.example-card::before` moves (`transition: transform 0.3s cubic-bezier(0.4, 0, 0.2, 1)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — apps/agent_web/priv/static/css/style.css:350
  • `.message` moves (`animation: fadeInUp 0.3s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — apps/agent_web/priv/static/css/style.css:390
  • `.status-indicator::before` moves (`animation: pulse 2s cubic-bezier(0.4, 0, 0.6, 1) infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — apps/agent_web/priv/static/css/style.css:463
  • `.status-indicator.pulsing` moves (`animation: pulse 2s infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — apps/agent_web/priv/static/css/style.css:767
  • `.connection.active` moves (`animation: flow 2s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — apps/agent_web/priv/static/css/style.css:820
  • `.notification` moves (`animation: slideIn 0.3s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — apps/agent_web/priv/static/css/style.css:1054

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.
AC7 · A11y enforcement4.0 / 10Weak✓ Tool-verified

Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an accessibility checker configured over the markup (an a11y lint rule set, e.g. eslint-plugin-jsx-a11y or vuejs-accessibility where the project lints JavaScript) and an automated accessibility assertion wired into tests or CI (axe/pa11y/Lighthouse or an equivalent) — on the Documented→Verified→Prevented ladder.

Method: Repo config/CI scan: an accessibility checker configured over the markup (an a11y lint rule set such as eslint-plugin-jsx-a11y / vuejs-accessibility where JavaScript is linted) and an automated accessibility assertion in tests or CI (axe/pa11y/Lighthouse or equivalent), graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.

Coverage: Population: the repository's own tooling configuration — lint config, test and CI files — NOT the markup. It is read for a configured accessibility checker and an automated accessibility assertion (axe/pa11y/Lighthouse, or a native-toolkit equivalent), and it credits an INVOCATION, never a mention: a licence filename, an import comment or a doc reference earns no rung. Enforcement configured entirely outside the repository leaves no evidence here and cannot be credited.

  • No accessibility enforcement found — no a11y linter (eslint-plugin-jsx-a11y) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 78 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here. — apps/agent_web/frontend/package.json:47

What to do

  • Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI.
AX10 · Code composition10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.

Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.

Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.

What to do

  • The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

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.

AX4 · Dependency direction10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.

Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.

AX9 · CQS / query purity10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.

Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.

Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.

  • `openapi_ai_transform` has a `handle_call` query clause that reads a store and, on the not-found (cache-miss) branch, WRITES it — a get-or-create that mutates as a side effect of a read. A query must stay side-effect-free so reads are safe to retry, cache, and route to a read replica; move the lazy-init write into a command. — apps/openapi_scaffold/src/openapi_ai_transform.erl:85

What to do

  • Keep query handlers read-only — move the writes/event-publishes into a command handler so reads stay safe to retry, cache, and route to a read replica.
ED1 · Handler temporal coupling4.8 / 10Adequate✓ Tool-verified

Other · Event-Driven — Whether event handlers stay asynchronous (no blocking remote HTTP/gRPC calls awaited inside a handler).

Method: Roslyn semantic scan (event-driven gated): event-handler bodies scanned for HTTP/gRPC invocations by resolved symbol type, not substring. Deterministic, semantic-resolved.

  • `distributed_error_coordinator` clause `handle_call/3#90` blocks on a hand-rolled `Pid ! Req, receive Resp` rendezvous awaiting a peer's reply while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, reply asynchronously (send-and-continue), or run the round-trip in a throwaway spawned process. — apps/agent_web/src/distributed_error_coordinator.erl:96
  • `embedding_integration` clause `handle_call/3#86` blocks the process on a synchronous outbound I/O client call (a remote HTTP request, a socket receive, or a blocking pool checkout) awaited inline while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, issue the request off the hot path — reply asynchronously and do the I/O in a throwaway spawned worker (or use the async client API), so the process keeps serving its mailbox. — apps/agent_web/src/embedding_integration.erl:410
  • `embedding_integration` clause `handle_call/3#117` blocks the process on a synchronous outbound I/O client call (a remote HTTP request, a socket receive, or a blocking pool checkout) awaited inline while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, issue the request off the hot path — reply asynchronously and do the I/O in a throwaway spawned worker (or use the async client API), so the process keeps serving its mailbox. — apps/agent_web/src/embedding_integration.erl:410
  • `embedding_integration` clause `handle_call/3#254` makes a synchronous `gen_server`/`gen_statem:call` round-trip to a peer process while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, react by casting a follow-up message (fire-and-forget), or resolve the needed state locally. — apps/agent_web/src/embedding_integration.erl:259
  • `mcp_client_v2` clause `handle_call/3#105` blocks the process on a synchronous outbound I/O client call (a remote HTTP request, a socket receive, or a blocking pool checkout) awaited inline while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, issue the request off the hot path — reply asynchronously and do the I/O in a throwaway spawned worker (or use the async client API), so the process keeps serving its mailbox. (×2) — apps/agent_web/src/mcp_client_v2.erl:327, apps/agent_web/src/mcp_client_v2.erl:757
  • `mcp_client_v2` clause `handle_call/3#208` blocks the process on a synchronous outbound I/O client call (a remote HTTP request, a socket receive, or a blocking pool checkout) awaited inline while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, issue the request off the hot path — reply asynchronously and do the I/O in a throwaway spawned worker (or use the async client API), so the process keeps serving its mailbox. — apps/agent_web/src/mcp_client_v2.erl:757
  • `mcp_client_v2` clause `handle_cast/2#225` blocks the process on a synchronous outbound I/O client call (a remote HTTP request, a socket receive, or a blocking pool checkout) awaited inline while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, issue the request off the hot path — reply asynchronously and do the I/O in a throwaway spawned worker (or use the async client API), so the process keeps serving its mailbox. — apps/agent_web/src/mcp_client_v2.erl:757
  • `mcp_client_v2` clause `handle_info/2#236` blocks the process on a synchronous outbound I/O client call (a remote HTTP request, a socket receive, or a blocking pool checkout) awaited inline while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, issue the request off the hot path — reply asynchronously and do the I/O in a throwaway spawned worker (or use the async client API), so the process keeps serving its mailbox. — apps/agent_web/src/mcp_client_v2.erl:757
  • `mcp_client_v2` clause `handle_info/2#240` blocks the process on a synchronous outbound I/O client call (a remote HTTP request, a socket receive, or a blocking pool checkout) awaited inline while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, issue the request off the hot path — reply asynchronously and do the I/O in a throwaway spawned worker (or use the async client API), so the process keeps serving its mailbox. — apps/agent_web/src/mcp_client_v2.erl:757
  • `mcp_client_v2` clause `handle_info/2#244` blocks the process on a synchronous outbound I/O client call (a remote HTTP request, a socket receive, or a blocking pool checkout) awaited inline while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, issue the request off the hot path — reply asynchronously and do the I/O in a throwaway spawned worker (or use the async client API), so the process keeps serving its mailbox. — apps/agent_web/src/mcp_client_v2.erl:757
  • `mcp_client_v2` clause `handle_info/2#276` blocks the process on a synchronous outbound I/O client call (a remote HTTP request, a socket receive, or a blocking pool checkout) awaited inline while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, issue the request off the hot path — reply asynchronously and do the I/O in a throwaway spawned worker (or use the async client API), so the process keeps serving its mailbox. — apps/agent_web/src/mcp_client_v2.erl:757
  • `mcp_client_v2` clause `handle_websocket_message/2#520` blocks the process on a synchronous outbound I/O client call (a remote HTTP request, a socket receive, or a blocking pool checkout) awaited inline while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, issue the request off the hot path — reply asynchronously and do the I/O in a throwaway spawned worker (or use the async client API), so the process keeps serving its mailbox. — apps/agent_web/src/mcp_client_v2.erl:757
  • `mcp_client_v2` clause `handle_sse_data/2#530` blocks the process on a synchronous outbound I/O client call (a remote HTTP request, a socket receive, or a blocking pool checkout) awaited inline while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, issue the request off the hot path — reply asynchronously and do the I/O in a throwaway spawned worker (or use the async client API), so the process keeps serving its mailbox. — apps/agent_web/src/mcp_client_v2.erl:757
  • `mcp_client_v2` clause `handle_response/3#622` blocks the process on a synchronous outbound I/O client call (a remote HTTP request, a socket receive, or a blocking pool checkout) awaited inline while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, issue the request off the hot path — reply asynchronously and do the I/O in a throwaway spawned worker (or use the async client API), so the process keeps serving its mailbox. — apps/agent_web/src/mcp_client_v2.erl:757
  • `mcp_github_registry_updater` clause `handle_info/2#94` blocks the process on a synchronous outbound I/O client call (a remote HTTP request, a socket receive, or a blocking pool checkout) awaited inline while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, issue the request off the hot path — reply asynchronously and do the I/O in a throwaway spawned worker (or use the async client API), so the process keeps serving its mailbox. — apps/agent_web/src/mcp_github_registry_updater.erl:161
  • `mcp_oauth_client` clause `handle_cast/2#126` blocks the process on a synchronous outbound I/O client call (a remote HTTP request, a socket receive, or a blocking pool checkout) awaited inline while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, issue the request off the hot path — reply asynchronously and do the I/O in a throwaway spawned worker (or use the async client API), so the process keeps serving its mailbox. — apps/agent_web/src/mcp_oauth_client.erl:269
  • `mcp_oauth_client` clause `handle_call/3#60` blocks the process on a synchronous outbound I/O client call (a remote HTTP request, a socket receive, or a blocking pool checkout) awaited inline while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, issue the request off the hot path — reply asynchronously and do the I/O in a throwaway spawned worker (or use the async client API), so the process keeps serving its mailbox. — apps/agent_web/src/mcp_oauth_client.erl:300
  • `mcp_oauth_client` clause `handle_call/3#89` blocks the process on a synchronous outbound I/O client call (a remote HTTP request, a socket receive, or a blocking pool checkout) awaited inline while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, issue the request off the hot path — reply asynchronously and do the I/O in a throwaway spawned worker (or use the async client API), so the process keeps serving its mailbox. — apps/agent_web/src/mcp_oauth_client.erl:300
  • `mcp_oauth_client` clause `handle_token_refresh/3#206` blocks the process on a synchronous outbound I/O client call (a remote HTTP request, a socket receive, or a blocking pool checkout) awaited inline while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, issue the request off the hot path — reply asynchronously and do the I/O in a throwaway spawned worker (or use the async client API), so the process keeps serving its mailbox. — apps/agent_web/src/mcp_oauth_client.erl:300
  • `mcp_oauth_integration` clause `handle_oauth_popup_callback/3#153` blocks the process on a synchronous outbound I/O client call (a remote HTTP request, a socket receive, or a blocking pool checkout) awaited inline while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, issue the request off the hot path — reply asynchronously and do the I/O in a throwaway spawned worker (or use the async client API), so the process keeps serving its mailbox. — apps/agent_web/src/mcp_oauth_integration.erl:217
  • `oauth_handler` clause `handle_request/4#86` blocks the process on a synchronous outbound I/O client call (a remote HTTP request, a socket receive, or a blocking pool checkout) awaited inline while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, issue the request off the hot path — reply asynchronously and do the I/O in a throwaway spawned worker (or use the async client API), so the process keeps serving its mailbox. — apps/agent_web/src/oauth_handler.erl:272
  • `oauth_handler` clause `handle_oauth_callback/3#135` blocks the process on a synchronous outbound I/O client call (a remote HTTP request, a socket receive, or a blocking pool checkout) awaited inline while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, issue the request off the hot path — reply asynchronously and do the I/O in a throwaway spawned worker (or use the async client API), so the process keeps serving its mailbox. — apps/agent_web/src/oauth_handler.erl:272
  • `oauth_manager` clause `handle_call/3#197` makes a synchronous `gen_server`/`gen_statem:call` round-trip to a peer process while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, react by casting a follow-up message (fire-and-forget), or resolve the needed state locally. — apps/agent_web/src/oauth_manager.erl:202
  • `openapi_fetcher` clause `handle_call/3#70` blocks the process on a synchronous outbound I/O client call (a remote HTTP request, a socket receive, or a blocking pool checkout) awaited inline while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, issue the request off the hot path — reply asynchronously and do the I/O in a throwaway spawned worker (or use the async client API), so the process keeps serving its mailbox. — apps/agent_web/src/openapi_fetcher.erl:164
  • `pipedream_mcp_client` clause `handle_call/3#83` blocks the process on a synchronous outbound I/O client call (a remote HTTP request, a socket receive, or a blocking pool checkout) awaited inline while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, issue the request off the hot path — reply asynchronously and do the I/O in a throwaway spawned worker (or use the async client API), so the process keeps serving its mailbox. — apps/agent_web/src/pipedream_mcp_client.erl:152
  • `pipedream_mcp_client` clause `handle_call/3#91` blocks the process on a synchronous outbound I/O client call (a remote HTTP request, a socket receive, or a blocking pool checkout) awaited inline while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, issue the request off the hot path — reply asynchronously and do the I/O in a throwaway spawned worker (or use the async client API), so the process keeps serving its mailbox. — apps/agent_web/src/pipedream_mcp_client.erl:191
  • `pipedream_mcp_client` clause `handle_call/3#95` blocks the process on a synchronous outbound I/O client call (a remote HTTP request, a socket receive, or a blocking pool checkout) awaited inline while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, issue the request off the hot path — reply asynchronously and do the I/O in a throwaway spawned worker (or use the async client API), so the process keeps serving its mailbox. — apps/agent_web/src/pipedream_mcp_client.erl:232
  • `pipedream_mcp_client` clause `handle_call/3#99` blocks the process on a synchronous outbound I/O client call (a remote HTTP request, a socket receive, or a blocking pool checkout) awaited inline while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, issue the request off the hot path — reply asynchronously and do the I/O in a throwaway spawned worker (or use the async client API), so the process keeps serving its mailbox. — apps/agent_web/src/pipedream_mcp_client.erl:270
  • `pipedream_mcp_client` clause `handle_call/3#103` blocks the process on a synchronous outbound I/O client call (a remote HTTP request, a socket receive, or a blocking pool checkout) awaited inline while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, issue the request off the hot path — reply asynchronously and do the I/O in a throwaway spawned worker (or use the async client API), so the process keeps serving its mailbox. — apps/agent_web/src/pipedream_mcp_client.erl:270
  • `agent` clause `handle_follow_up/3#692` makes a synchronous `gen_server`/`gen_statem:call` round-trip to a peer process while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, react by casting a follow-up message (fire-and-forget), or resolve the needed state locally. — apps/agents/src/agent.erl:694
  • `agent_messenger` clause `handle_call/3#93` blocks on a hand-rolled `Pid ! Req, receive Resp` rendezvous awaiting a peer's reply while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, reply asynchronously (send-and-continue), or run the round-trip in a throwaway spawned process. — apps/agents/src/agent_messenger.erl:97
  • `enhanced_agent_tools` clause `handle_call/3#112` blocks the process on a synchronous outbound I/O client call (a remote HTTP request, a socket receive, or a blocking pool checkout) awaited inline while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, issue the request off the hot path — reply asynchronously and do the I/O in a throwaway spawned worker (or use the async client API), so the process keeps serving its mailbox. — apps/agents/src/enhanced_agent_tools.erl:364
  • `meta_server` clause `handle_connection/1#295` blocks the process on a synchronous outbound I/O client call (a remote HTTP request, a socket receive, or a blocking pool checkout) awaited inline while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, issue the request off the hot path — reply asynchronously and do the I/O in a throwaway spawned worker (or use the async client API), so the process keeps serving its mailbox. (×3) — apps/agents/src/meta_server.erl:296, apps/agents/src/meta_server.erl:306, apps/agents/src/meta_server.erl:323
  • `openai_chat` clause `handle_call/3#93` blocks the process on a synchronous outbound I/O client call (a remote HTTP request, a socket receive, or a blocking pool checkout) awaited inline while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, issue the request off the hot path — reply asynchronously and do the I/O in a throwaway spawned worker (or use the async client API), so the process keeps serving its mailbox. — apps/openai/src/openai_chat.erl:224
  • `openai_files` clause `handle_call/3#154` blocks the process on a synchronous outbound I/O client call (a remote HTTP request, a socket receive, or a blocking pool checkout) awaited inline while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, issue the request off the hot path — reply asynchronously and do the I/O in a throwaway spawned worker (or use the async client API), so the process keeps serving its mailbox. — apps/openai/src/openai_files.erl:243
  • `openai_files` clause `handle_call/3#171` blocks the process on a synchronous outbound I/O client call (a remote HTTP request, a socket receive, or a blocking pool checkout) awaited inline while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, issue the request off the hot path — reply asynchronously and do the I/O in a throwaway spawned worker (or use the async client API), so the process keeps serving its mailbox. — apps/openai/src/openai_files.erl:278
  • `openai_files` clause `handle_call/3#180` blocks the process on a synchronous outbound I/O client call (a remote HTTP request, a socket receive, or a blocking pool checkout) awaited inline while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, issue the request off the hot path — reply asynchronously and do the I/O in a throwaway spawned worker (or use the async client API), so the process keeps serving its mailbox. — apps/openai/src/openai_files.erl:305

What to do

  • Remove synchronous peer round-trips (gen_server:call / hand-rolled receive) and blocking sleeps from OTP message handlers — cast a follow-up or resolve state locally, so processes stay temporally decoupled and deadlock-free.
ED2 · Event/command shape7.9 / 10Strong✓ Tool-verified

Other · Event-Driven — Whether commands have exactly one owning handler (no hidden fan-out).

Method: Roslyn scan (event-driven gated): command-shaped messages identified by convention; handler count per command checked for the exactly-one rule. Deterministic, hard fact.

  • `create_swarm` is shaped like a command (one imperative intent) but is handled synchronously by more than one module — a command should have exactly one owning handler. Split the responsibilities, or raise an EVENT after the command and let the others subscribe. (×3) — apps/agents/src/cluster_orchestrator.erl:138, apps/agents/src/emergent_swarm_intelligence.erl:237, apps/agents/src/swarm_intelligence_engine.erl:131

What to do

  • Give each command exactly one owning handler; use events for fan-out.
ES1 · Fold determinism5.4 / 10Adequate✓ Tool-verified

Other · Event Sourcing — Whether the event-sourcing replay fold reconstructs state purely from the event (no wall clock, UUID or randomness) so replay is reproducible.

Method: Roslyn syntax scan (event-sourcing gated): Apply/When folds checked for forbidden tokens (DateTime.Now, Guid.NewGuid, Random, IO), stripped of comments/strings. Deterministic, hard fact per fold.

  • `agent_api_handler`'s event-replay reducer reads a wall clock / randomness / a peer process / persistence while reconstructing aggregate state — replaying the same events would rebuild DIFFERENT state each run. A fold must be a pure function of (state, event); stamp the timestamp/id into the event at raise-time and read it back in the fold. — apps/agent_web/src/agent_api_handler.erl:306

What to do

  • Keep the event-replay reducer pure — move every clock/UUID/random into the event at raise-time and read it back in the fold.
ES2 · Immutable events10.0 / 10Exemplary✓ Tool-verified

Other · Event Sourcing — Whether persisted events stay immutable (never rewritten in place).

Method: Roslyn scan (event-sourcing gated): persisted events checked for public setters; immutability verified per property/field. Deterministic, hard fact.

M1 · Documentation (README)9.3 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.

Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.

What to do

  • Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
M2 · Architecture documentation5.0 / 10Adequate✓ Tool-verified

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.
M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.

Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.

M4 · Documentation accuracy10.0 / 10Exemplary○ Nothing flagged

Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).

Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.

P1 · CI/CD gates0.0 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether an automated pipeline builds and tests every change.

Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.

  • No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.

What to do

  • Add a CI workflow that builds and runs the test suite on every push/PR.
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 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.

P2 · Observability8.0 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.

Method: Filesystem/Roslyn scan: structured-logging frameworks (Serilog, NLog), OpenTelemetry, and health-check endpoint patterns. Exhaustive, deterministic.

  • Only 1/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `sandbox/myapp`.

What to do

  • Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
P3 · Security & performance tooling0.0 / 10Critical✓ Tool-verified

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 dialyzer or elvis — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
  • `apps/agent_web/frontend/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — apps/agent_web/frontend/package.json:11

What to do

  • Run what this repository's stack ships: dialyzer or elvis — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
  • Enable Dependabot/Renovate or a dependency-review gate.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene5.0 / 10Adequate✓ Tool-verified

Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.

Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.

  • No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)

What to do

  • Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
P7 · Outbound HTTP resilience3.0 / 10Weak✓ Tool-verified

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.

  • `httpc:request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×17) — apps/agent_web/src/embedding_integration.erl:410, apps/agent_web/src/mcp_oauth_client.erl:269, apps/agent_web/src/mcp_oauth_client.erl:300, …
  • `hackney: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. — apps/openapi_scaffold/src/openapi_graphql_bridge.erl:641
  • `hackney:request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×3) — apps/openapi_scaffold/src/openapi_graphql_bridge.erl:665, apps/openapi_scaffold/src/openapi_playground.erl:583, apps/openapi_scaffold/src/openapi_time_travel.erl:352
  • `gun:open(` 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. — apps/openapi_scaffold/src/openapi_graphql_bridge.erl:788

What to do

  • Pass an explicit bound on every request — `{timeout, Ms}` in `httpc:request/4`'s HTTP options (its default is `infinity`), `{recv_timeout, Ms}` for hackney, a timeout on `gun:await/3` — and wrap dependencies that fail in a breaker (`fuse`) with back-off (`backoff`).
PF3 · Async & latency hygiene10.0 / 10Exemplary✓ Tool-verified

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 the language 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.

R1 · Type Safety9.9 / 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.

What to do

  • Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication8.1 / 10Strong✓ Tool-verified

React / JS · Code Health — Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm over JS/TS tokens, D-386): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.

Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Deterministic.

  • REDACTED:642 · REDACTED:1499 — the two spans are one implementation copied and then locally edited — 157 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — REDACTED:642
  • apps/agent_web/frontend/src/components/AdvancedMessageRenderer.tsx:171 · apps/agent_web/frontend/src/components/AdvancedMessageRenderer.tsx:232 — the two spans are one implementation copied and then locally edited — 194 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — apps/agent_web/frontend/src/components/AdvancedMessageRenderer.tsx:171
  • apps/agent_web/frontend/src/components/InteractiveReasoningControls.tsx:310 · apps/agent_web/frontend/src/components/InteractiveReasoningControls.tsx:417 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — apps/agent_web/frontend/src/components/InteractiveReasoningControls.tsx:310
  • apps/agent_web/frontend/src/components/ComprehensiveMCPManager.tsx:453 · apps/agent_web/frontend/src/components/ComprehensiveMCPManager.tsx:541 — 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. — apps/agent_web/frontend/src/components/ComprehensiveMCPManager.tsx:453
  • apps/agent_web/frontend/src/components/ComprehensiveMCPManager.tsx:500 · apps/agent_web/frontend/src/components/ComprehensiveMCPManager.tsx:601 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — apps/agent_web/frontend/src/components/ComprehensiveMCPManager.tsx:500
  • apps/agent_web/frontend/src/components/VirtualizedAgentList.tsx:98 · apps/agent_web/frontend/src/components/VirtualizedAgentList.tsx:146 — 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. — apps/agent_web/frontend/src/components/VirtualizedAgentList.tsx:98
  • apps/agent_web/frontend/src/components/AdaptiveAIInterface.tsx:367 · apps/agent_web/frontend/src/components/QuantumConsciousnessInterface.tsx:376 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — apps/agent_web/frontend/src/components/AdaptiveAIInterface.tsx:367
  • apps/agent_web/frontend/src/components/CrashMonitorDashboard.tsx:319 · apps/agent_web/frontend/src/components/ErrorInterpretationPanel.tsx:230 — 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. — apps/agent_web/frontend/src/components/CrashMonitorDashboard.tsx:319
  • apps/agent_web/frontend/src/components/ComprehensiveMCPManager.tsx:763 · apps/agent_web/frontend/src/components/ComprehensiveMCPManager.tsx:833 — 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. — apps/agent_web/frontend/src/components/ComprehensiveMCPManager.tsx:763
  • apps/agent_web/frontend/src/components/CrashMonitorDashboard.tsx:414 · apps/agent_web/frontend/src/components/ErrorInterpretationPanel.tsx:319 — 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. — apps/agent_web/frontend/src/components/CrashMonitorDashboard.tsx:414
  • apps/agent_web/frontend/src/components/InteractiveReasoningControls.tsx:392 · apps/agent_web/frontend/src/components/InteractiveReasoningControls.tsx:453 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — apps/agent_web/frontend/src/components/InteractiveReasoningControls.tsx:392
  • apps/agent_web/frontend/src/components/UltimatePerformanceDashboard.tsx:432 · apps/agent_web/frontend/src/components/UltimatePerformanceDashboard.tsx:468 — 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. — apps/agent_web/frontend/src/components/UltimatePerformanceDashboard.tsx:432
  • apps/agent_web/frontend/src/components/UltraAdvancedDashboard.tsx:621 · apps/agent_web/frontend/src/components/UltraAdvancedDashboard.tsx:645 · apps/agent_web/frontend/src/components/UltraAdvancedDashboard.tsx:669 — 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. — apps/agent_web/frontend/src/components/UltraAdvancedDashboard.tsx:621
  • apps/agent_web/frontend/src/components/CrashMonitorDashboard.tsx:442 · apps/agent_web/frontend/src/components/ErrorInterpretationPanel.tsx:352 — 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. — apps/agent_web/frontend/src/components/CrashMonitorDashboard.tsx:442
  • apps/agent_web/frontend/src/components/CrashMonitorDashboard.tsx:220 · apps/agent_web/frontend/src/components/MCPOrchestrationEngine.tsx:373 — the two spans are one implementation copied and then locally edited — 72 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. — apps/agent_web/frontend/src/components/CrashMonitorDashboard.tsx:220
  • apps/agent_web/frontend/src/components/MCPOAuthManager.tsx:148 · apps/agent_web/frontend/src/components/MCPOAuthManager.tsx:170 — 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. — apps/agent_web/frontend/src/components/MCPOAuthManager.tsx:148
  • apps/agent_web/frontend/src/components/MultiAgentChat.tsx:483 · REDACTED:1009 — 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. — apps/agent_web/frontend/src/components/MultiAgentChat.tsx:483
  • apps/agent_web/frontend/src/components/MCPServerManager.tsx:143 · apps/agent_web/frontend/src/components/MCPServerManager.tsx:173 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — apps/agent_web/frontend/src/components/MCPServerManager.tsx:143
  • apps/agent_web/frontend/src/components/ResourceSentinelBar.tsx:100 · apps/agent_web/frontend/src/components/ResourceSentinelBar.tsx:119 — 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. — apps/agent_web/frontend/src/components/ResourceSentinelBar.tsx:100
  • apps/agent_web/frontend/src/components/ui/select.tsx:33 · apps/agent_web/frontend/src/components/ui/select.tsx:50 — all 2 copies are in the same file, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — apps/agent_web/frontend/src/components/ui/select.tsx:33
  • REDACTED:1787 · REDACTED:1869 — 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. — REDACTED:1787
  • REDACTED:392 · apps/agent_web/frontend/src/components/MCPServerManager.tsx:69 — the two spans are one implementation copied and then locally edited — 69 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — REDACTED:392
  • apps/agent_web/frontend/src/components/AdvancedStructuredOutputsManager.tsx:320 · apps/agent_web/frontend/src/components/AdvancedStructuredOutputsManager.tsx:425 · apps/agent_web/frontend/src/components/AdvancedStructuredOutputsManager.tsx:493 · apps/agent_web/frontend/src/components/AdvancedStructuredOutputsManager.tsx:565 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — apps/agent_web/frontend/src/components/AdvancedStructuredOutputsManager.tsx:320
  • apps/agent_web/frontend/src/components/MCPOrchestrationEngine.tsx:587 · apps/agent_web/frontend/src/components/MCPOrchestrationEngine.tsx:604 — 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. — apps/agent_web/frontend/src/components/MCPOrchestrationEngine.tsx:587
  • apps/agent_web/frontend/src/components/PipedreamConnectionManager.tsx:83 · apps/agent_web/frontend/src/components/PipedreamConnectionManager.tsx:99 — 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. — apps/agent_web/frontend/src/components/PipedreamConnectionManager.tsx:83
  • apps/agent_web/frontend/src/components/PipedreamConnectionManager.tsx:128 · apps/agent_web/frontend/src/components/PipedreamConnectionManager.tsx:152 — 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. — apps/agent_web/frontend/src/components/PipedreamConnectionManager.tsx:128
  • apps/agent_web/frontend/src/components/ApiKeyManager.tsx:333 · apps/agent_web/frontend/src/components/FleetManagementDashboard.tsx:391 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — apps/agent_web/frontend/src/components/ApiKeyManager.tsx:333
  • apps/agent_web/frontend/src/components/CommandPalette.tsx:124 · apps/agent_web/frontend/src/components/CommandPalette.tsx:187 — 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. — apps/agent_web/frontend/src/components/CommandPalette.tsx:124
  • REDACTED:84 · REDACTED:178 — 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. — REDACTED:84
  • apps/agent_web/frontend/src/components/ExamplesPanel.tsx:11 · REDACTED:711 — the two spans are one implementation copied and then locally edited — 82 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. — apps/agent_web/frontend/src/components/ExamplesPanel.tsx:11
  • apps/agent_web/frontend/src/components/ModelConfiguration.tsx:311 · apps/agent_web/frontend/src/components/ModelConfiguration.tsx:325 · apps/agent_web/frontend/src/components/ModelConfiguration.tsx:340 — 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. — apps/agent_web/frontend/src/components/ModelConfiguration.tsx:311
  • apps/agent_web/frontend/src/components/RightDrawerInspector.tsx:192 · apps/agent_web/frontend/src/components/RightDrawerInspector.tsx:230 — 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. — apps/agent_web/frontend/src/components/RightDrawerInspector.tsx:192
  • apps/agent_web/frontend/src/components/AdaptiveAIInterface.tsx:407 · apps/agent_web/frontend/src/components/AdaptiveAIInterface.tsx:452 · apps/agent_web/frontend/src/components/AdaptiveAIInterface.tsx:497 · apps/agent_web/frontend/src/components/ApiKeyManager.tsx:336 · +5 more site(s) not listed — the 3 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — apps/agent_web/frontend/src/components/AdaptiveAIInterface.tsx:407
  • REDACTED:466 · apps/agent_web/frontend/src/components/OAuthManager.tsx:299 — 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. — REDACTED:466
  • apps/agent_web/frontend/src/components/ComprehensiveMCPManager.tsx:877 · apps/agent_web/frontend/src/components/ComprehensiveMCPManager.tsx:891 — 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. — apps/agent_web/frontend/src/components/ComprehensiveMCPManager.tsx:877
  • apps/agent_web/frontend/src/components/QuantumConsciousnessInterface.tsx:396 · apps/agent_web/frontend/src/components/QuantumConsciousnessInterface.tsx:466 · apps/agent_web/frontend/src/components/QuantumConsciousnessInterface.tsx:509 · apps/agent_web/frontend/src/components/QuantumConsciousnessInterface.tsx:568 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — apps/agent_web/frontend/src/components/QuantumConsciousnessInterface.tsx:396
  • REDACTED:974 · REDACTED:990 — 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:974
  • apps/agent_web/frontend/src/components/AdaptiveAIInterface.tsx:467 · apps/agent_web/frontend/src/components/AdaptiveAIInterface.tsx:480 — 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. — apps/agent_web/frontend/src/components/AdaptiveAIInterface.tsx:467
  • REDACTED:938 · REDACTED:951 · REDACTED:965 · REDACTED:979 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — REDACTED:938
  • apps/agent_web/frontend/src/components/AdvancedMessageRenderer.tsx:225 · apps/agent_web/frontend/src/components/AdvancedMessageRenderer.tsx:259 — 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. — apps/agent_web/frontend/src/components/AdvancedMessageRenderer.tsx:225

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.
R2 · Cyclomatic Complexity7.9 / 10Strong✓ Tool-verified

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.

  • SystemMonitoringDashboard has cyclomatic complexity 25 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — apps/agent_web/frontend/src/components/SystemMonitoringDashboard.tsx:65
  • ContentAnalysisBadge has cyclomatic complexity 20 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. — REDACTED:323
  • DiscoveryMeshDashboard 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. — apps/agent_web/frontend/src/components/DiscoveryMeshDashboard.tsx:55
  • analyzeContent has cyclomatic complexity 18 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. — apps/agent_web/frontend/src/components/AdvancedMessageRenderer.tsx:43
  • ErrorInterpretationPanel has cyclomatic complexity 18 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. — apps/agent_web/frontend/src/components/ErrorInterpretationPanel.tsx:55
  • Dashboard 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. — REDACTED:47
  • SimpleAdvancedChat 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. — REDACTED:384
  • CrashMonitorDashboard 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. — apps/agent_web/frontend/src/components/CrashMonitorDashboard.tsx:86
  • sendMessage 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. — REDACTED:792
  • DenseLayout has cyclomatic complexity 13 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — apps/agent_web/frontend/src/components/DenseLayout.tsx:14
  • InteractiveReasoningControls has cyclomatic complexity 13 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — apps/agent_web/frontend/src/components/InteractiveReasoningControls.tsx:53
  • ServerDetailPanel has cyclomatic complexity 12 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:1222
  • MCPServerManager has cyclomatic complexity 12 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — apps/agent_web/frontend/src/components/MCPServerManager.tsx:23
  • MultiAgentChat has cyclomatic complexity 12 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — apps/agent_web/frontend/src/components/MultiAgentChat.tsx:39
  • ChainOfThoughtVisualization has cyclomatic complexity 12 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. — apps/agent_web/frontend/src/components/ChainOfThoughtVisualization.tsx:52
  • handleWebSocketMessage has cyclomatic complexity 12 and cognitive complexity 9; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:527

What to do

  • Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
R3 · Large Files0.0 / 10Critical✓ 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.

  • REDACTED has 1830 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
  • REDACTED has 1440 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
  • REDACTED has 1125 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
  • apps/agent_web/frontend/src/components/MCPOrchestrationEngine.tsx has 1003 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/agent_web/frontend/src/components/MCPOrchestrationEngine.tsx:1
  • apps/agent_web/frontend/src/components/ComprehensiveMCPManager.tsx has 992 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/agent_web/frontend/src/components/ComprehensiveMCPManager.tsx:1
  • apps/agent_web/frontend/src/components/ModelTypeEditor.tsx has 850 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/agent_web/frontend/src/components/ModelTypeEditor.tsx:1
  • apps/agent_web/frontend/src/components/UltraAdvancedDashboard.tsx has 844 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/agent_web/frontend/src/components/UltraAdvancedDashboard.tsx:1
  • apps/agent_web/frontend/src/App.tsx has 673 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/agent_web/frontend/src/App.tsx:1
  • apps/agent_web/frontend/src/services/CollaborationManager.ts has 644 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/agent_web/frontend/src/services/CollaborationManager.ts:1
  • apps/agent_web/frontend/src/components/CrashMonitorDashboard.tsx has 636 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/agent_web/frontend/src/components/CrashMonitorDashboard.tsx:1
  • apps/agent_web/frontend/src/services/ChainOfThoughtEngine.ts has 619 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/agent_web/frontend/src/services/ChainOfThoughtEngine.ts:1
  • apps/agent_web/frontend/src/components/UltimatePerformanceDashboard.tsx has 589 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/agent_web/frontend/src/components/UltimatePerformanceDashboard.tsx:1
  • apps/agent_web/frontend/src/components/InteractiveWidgets.tsx has 572 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/agent_web/frontend/src/components/InteractiveWidgets.tsx:1
  • apps/agent_web/frontend/src/components/InteractiveReasoningControls.tsx has 569 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/agent_web/frontend/src/components/InteractiveReasoningControls.tsx:1
  • apps/agent_web/frontend/src/components/ModelConfiguration.tsx has 569 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/agent_web/frontend/src/components/ModelConfiguration.tsx:1
  • apps/agent_web/frontend/src/components/AdvancedStructuredOutputsManager.tsx has 562 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/agent_web/frontend/src/components/AdvancedStructuredOutputsManager.tsx:1
  • apps/agent_web/frontend/src/components/QuantumConsciousnessInterface.tsx has 562 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/agent_web/frontend/src/components/QuantumConsciousnessInterface.tsx:1
  • apps/agent_web/frontend/src/components/DiscoveryMeshDashboard.tsx has 558 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/agent_web/frontend/src/components/DiscoveryMeshDashboard.tsx:1
  • apps/agent_web/frontend/src/components/AdaptiveAIInterface.tsx has 542 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/agent_web/frontend/src/components/AdaptiveAIInterface.tsx:1
  • apps/agent_web/frontend/src/components/Timeline.tsx has 542 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/agent_web/frontend/src/components/Timeline.tsx:1
  • apps/agent_web/frontend/src/components/ToolRegistry.tsx has 526 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/agent_web/frontend/src/components/ToolRegistry.tsx:1
  • apps/agent_web/frontend/src/components/DynamicUIManager.tsx has 503 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/agent_web/frontend/src/components/DynamicUIManager.tsx:1
  • apps/agent_web/frontend/src/components/SystemMonitoringDashboard.tsx has 502 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/agent_web/frontend/src/components/SystemMonitoringDashboard.tsx:1
  • apps/agent_web/frontend/src/components/MultiAgentChat.tsx has 499 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/agent_web/frontend/src/components/MultiAgentChat.tsx:1
  • apps/agent_web/frontend/src/components/ChainOfThoughtVisualization.tsx has 489 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/agent_web/frontend/src/components/ChainOfThoughtVisualization.tsx:1
  • apps/agent_web/frontend/src/components/ErrorInterpretationPanel.tsx has 481 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/agent_web/frontend/src/components/ErrorInterpretationPanel.tsx:1
  • apps/agent_web/frontend/src/services/ContextualRetrieval.ts has 479 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/agent_web/frontend/src/services/ContextualRetrieval.ts:1
  • apps/agent_web/frontend/src/components/OAuthManager.tsx has 463 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/agent_web/frontend/src/components/OAuthManager.tsx:1
  • apps/agent_web/frontend/src/components/FleetManagementDashboard.tsx has 448 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/agent_web/frontend/src/components/FleetManagementDashboard.tsx:1
  • apps/agent_web/frontend/src/components/PipedreamConnectionManager.tsx has 430 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/agent_web/frontend/src/components/PipedreamConnectionManager.tsx:1
  • apps/agent_web/frontend/src/components/AdvancedMessageRenderer.tsx has 407 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/agent_web/frontend/src/components/AdvancedMessageRenderer.tsx:1

What to do

  • Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage0.0 / 10Critical✓ Tool-verified

React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.

Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.

  • 0% of 83 production file(s) reachable from 0 test file(s) via the import graph — 'production' here is the RESIDUE: every source file left once tests, tooling, generated output, config, declarations and declaration-only modules, fixture corpora, type fixtures, behaviour-free data modules, re-export barrels, registration/constant data modules and service workers are set aside, so the percentage is taken over a smaller denominator than the workspace's file count

What to do

  • Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness6.6 / 10Strong✓ Tool-verified

React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).

Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.

  • 34 outdated package(s); JS/npm CVEs scored in D30

What to do

  • Bump outdated dependencies to current versions to limit upgrade debt.
R6 · Tooling6.7 / 10Strong✓ Tool-verified

React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.

Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.

  • test ✓ · lint ✗ · typecheck ✓ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.

What to do

  • Add eslint as package.json scripts and run them in CI.
R7 · Dead Code0.0 / 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.

  • Unreachable from the 3 application, 3 tooling and 0 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
  • no import path from any entry point (3 application, 3 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×16) — apps/agent_web/frontend/src/components/ComprehensiveMCPManager.tsx, apps/agent_web/frontend/src/components/UltraAdvancedDashboard.tsx, apps/agent_web/frontend/src/components/ModelTypeEditor.tsx, …
  • no import path from any entry point (3 application, 3 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/agent_web/frontend/src/components/DynamicUIManager.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 (×2) — apps/agent_web/frontend/src/services/ContextualRetrieval.ts, apps/agent_web/frontend/src/components/AdvancedMessageRenderer.tsx
  • no import path from any entry point (3 application, 3 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/agent_web/frontend/src/components/MainLayoutWithSidebar.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 — apps/agent_web/frontend/src/components/ClaudeCLI.tsx
  • no import path from any entry point (3 application, 3 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (REDACTED) — 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) — apps/agent_web/frontend/src/components/AgentQuorumPanel.tsx, apps/agent_web/frontend/src/components/AgentCommunicationPanel.tsx
  • no import path from any entry point (3 application, 3 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/agent_web/frontend/src/components/ComprehensiveMCPManager.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 — apps/agent_web/frontend/src/components/MCPOAuthManager.tsx
  • Nothing imports this binding — it is safe to review for removal. (×2) — apps/agent_web/frontend/src/utils/sanitize.ts:90, apps/agent_web/frontend/src/utils/sanitize.ts:102
  • Nothing in its class reads or assigns this private field (for a constructor parameter property: it is stored and never read), and no string key or test reaches it by name. Remove it, or use it where it was meant to take effect. — apps/agent_web/frontend/src/services/ChainOfThoughtEngine.ts:77

What to do

  • Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene3.5 / 10Weak✓ Tool-verified

React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.

Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.

  • Imported but not declared in any reachable package.json — installs work only by hoisting accident. (×2) — REDACTED:13, REDACTED:12
  • Declared in apps/agent_web/frontend/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×3)

What to do

  • Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports10.0 / 10Exemplary✓ 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.

S1 · Web-Security Posture8.0 / 10Strong✓ Tool-verified

Other · Security — Only what this repository's own non-C# files could be read for was assessed — markup this repository SHIPS is scored for third-party script integrity whether or not the repository serves it itself, since a page handed to a consumer runs in that consumer’s origin. Nothing else in this dimension was assessed: the transport, cookie, input-validation and crypto controls are read from a source model that was not loaded for this repository’s language, so their absence here is not a finding about this repository.

Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.

  • `https://unpkg.com/react@18/umd/react.production.min.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. 6 such include(s) across the repository's markup. — REDACTED:7

What to do

  • Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
X1 · Async correctness7.8 / 10Strong✓ Tool-verified

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.

  • `forEach` ignores what its callback returns, so the Promise each `async` call returns is dropped: nothing can await it, the code after this loop runs before any of the awaited work has finished (a function that `await`s around this loop still returns early), and a rejection is never handled — in Node.js an unhandled rejection terminates the process by default, and in a browser it is lost. Iterate with `for (const item of items) { await … }` when the work must run in order, or `await Promise.all(items.map(async (item) => { … }))` when it may run concurrently, so the enclosing function finishes only when the work does and its failures reach the caller. Where firing and forgetting is genuinely intended, make the callback's whole body a `try { … } catch (e) { … }` that handles the failure, so it cannot escape. — apps/agent_web/frontend/src/components/MultiAgentChat.tsx:387

What to do

  • `async` callback passed to `forEach`
X12 · Unreachable branch10.0 / 10Exemplary○ Nothing flagged

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.

X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.

Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.

X14 · Bypassable address classification10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.

Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.

X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.

Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.

X16 · Unfloored truncation loop10.0 / 10Exemplary○ Nothing flagged

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.

X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.

Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.

X18 · Disposal-pattern correctness10.0 / 10Exemplary○ Nothing flagged

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.

X19 · Unrestored process-global state10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.

Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.

X2 · Cancellation propagation4.1 / 10Weak✓ Tool-verified

Other · Code Health — Whether async functions that make a cancellable request accept or pass on an AbortSignal (adoption curve).

Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.

  • Only 1/54 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
  • `loadAgents` 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 })`. — REDACTED:476
  • `createAgent` 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) — REDACTED:659, apps/agent_web/frontend/src/hooks/useAgents.tsx:177
  • `runExample` 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 })`. — REDACTED:709
  • `sendSimpleMessage` 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 })`. — REDACTED:771
  • `loadAnalytics` 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 })`. — REDACTED:990
  • `viewAgentDetails` 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 })`. — REDACTED:1031
  • `createFromTemplate` 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 })`. — REDACTED:1065
  • `stopAgent` 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 })`. — REDACTED:1393
  • `loadKnowledgeDomains` 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 })`. — REDACTED:1640
  • `loadDomainInfo` 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 })`. — REDACTED:1695
  • `loadKnowledgeStatus` 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 })`. — REDACTED:1732
  • `discoverNewDomains` 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 })`. — REDACTED:1772
  • `startIngestion` 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 })`. — REDACTED:1835
  • `loadDomainsForSearch` 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 })`. — REDACTED:1910
  • `performSearch` 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 })`. — REDACTED:1926
  • `viewDomainContents` 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 })`. — REDACTED:2007
  • `loadSystemMetrics` 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 })`. — apps/agent_web/frontend/src/App.tsx:131
  • `logButtonClick` 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 })`. — apps/agent_web/frontend/src/App.tsx:154
  • `logError` 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 })`. — apps/agent_web/frontend/src/App.tsx:189
  • `loadInitialAgents` 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 })`. — apps/agent_web/frontend/src/hooks/useAgents.tsx:32
  • `refreshAgents` 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 })`. — apps/agent_web/frontend/src/hooks/useAgents.tsx:167
  • `deleteAgent` 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 })`. — apps/agent_web/frontend/src/hooks/useAgents.tsx:196
  • `checkServerHealth` 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 })`. — REDACTED:252
  • `loadApiKeyStatus` 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 })`. — apps/agent_web/frontend/src/components/ApiKeyManager.tsx:69
  • `loadServiceKeys` 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 })`. — apps/agent_web/frontend/src/components/ApiKeyManager.tsx:89
  • `checkApiKeys` 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 })`. — apps/agent_web/frontend/src/components/ApiKeyNotification.tsx:19
  • `loadMCPStatus` 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 })`. — apps/agent_web/frontend/src/components/ComprehensiveMCPManager.tsx:118
  • `fetchAnalysis` 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 })`. — apps/agent_web/frontend/src/components/CrashMonitorDashboard.tsx:186
  • `fetchFixes` 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 })`. — apps/agent_web/frontend/src/components/CrashMonitorDashboard.tsx:198
  • `loadDiscoveryHistory` 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 })`. — apps/agent_web/frontend/src/components/DiscoveryMeshDashboard.tsx:90
  • `loadSupervisionTree` 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 })`. — REDACTED:156
  • `checkOAuthStatus` 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 })`. — apps/agent_web/frontend/src/components/MCPOAuthManager.tsx:96
  • `loadServersAndWorkflows` 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 })`. — apps/agent_web/frontend/src/components/MCPOrchestrationEngine.tsx:202
  • `startAIAnalysis` 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 })`. — apps/agent_web/frontend/src/components/MCPOrchestrationEngine.tsx:222
  • `updateMetrics` 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 })`. — apps/agent_web/frontend/src/components/MCPOrchestrationEngine.tsx:311
  • `runAutoOptimization` 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 })`. — apps/agent_web/frontend/src/components/MCPOrchestrationEngine.tsx:344
  • `fetchServers` 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 })`. — apps/agent_web/frontend/src/components/MCPServerManager.tsx:42
  • `loadModels` 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 })`. — apps/agent_web/frontend/src/components/ModelTypeEditor.tsx:94

What to do

  • Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

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.

X22 · Contradicted release guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.

Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.

X23 · Unguarded diagnostic materialisation10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.

Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.

X24 · Document value interpolated into markup unescaped2.8 / 10Weak✓ Tool-verified

Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.

Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.

  • `html` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — apps/agent_web/frontend/src/utils/sanitize.ts:22
  • `agent.id` is text this program did not author, and it is written into a script or style context through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. A script or style context needs its own escaping (or a JSON serialiser that escapes `<`); better, pass the value through a data attribute. (×2) — REDACTED:502, REDACTED:984
  • `agent.type` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:504
  • `data.system.node` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:958
  • `this.formatBytes(data.system.total_memory)` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:959
  • `data.system.process_count` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:960
  • `data.system.schedulers` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:961
  • `agent.meta.name||'Unnamed'` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:979
  • `String(agent.id).substring(0,8)` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:980
  • `agent.status` is text this program did not author, and it is written into a quoted attribute value through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:981
  • `this.formatBytes(agent.memory)` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:982
  • `agent.message_queue` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:983
  • `t.name` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:1021
  • `t.description` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:1022
  • `t.id` is text this program did not author, and it is written into a script or style context through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. A script or style context needs its own escaping (or a JSON serialiser that escapes `<`); better, pass the value through a data attribute. — REDACTED:1023
  • `String(agentId).substring(0,8)` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:1048
  • `JSON.stringify(data.agent_state,null,2)` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:1051
  • `JSON.stringify(data.performance,null,2)` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:1054
  • `JSON.stringify(data.process_info,null,2)` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:1057
  • `activity.type` is text this program did not author, and it is written into a quoted attribute value through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:1252
  • `activity.title` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:1254
  • `activity.description` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:1255
  • `new Date().toLocaleTimeString()` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:1256
  • `activityHtml+feed.innerHTML` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:1261
  • `type.charAt(0).toUpperCase()+type.slice(1)` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:1290
  • `message` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:1291
  • `domain` is text this program did not author, and it is written into a quoted attribute value through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×3) — REDACTED:1677, REDACTED:1685, REDACTED:1918
  • `domain` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:1679
  • `domain` is text this program did not author, and it is written into a script or style context through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. A script or style context needs its own escaping (or a JSON serialiser that escapes `<`); better, pass the value through a data attribute. (×2) — REDACTED:1681, REDACTED:1682
  • `[...new Set(data.contents.map(c=>c.type))].join(', ')` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:1707
  • `file.file` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:1711
  • `this.formatBytes(file.size)` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:1712
  • `data.error` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:1722
  • `error.message` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:1727
  • `data.queue_length||0` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:1744
  • `data.active_jobs||0` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:1748

What to do

  • Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
X25 · Inert configuration knob10.0 / 10Exemplary○ Nothing flagged

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.

X26 · Unsynchronised callback handoff10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.

Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.

X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a walk over an ETS table leaves the key it stands on alone — Erlang's own lists and maps are values no body can change, but an ETS key traversal asks the table for the key after the current one, so on a `set`, `bag` or `duplicate_bag` that is not fixed with `ets:safe_fixtable/2`, deleting the current key and then calling `ets:next/2` (or `ets:prev/2`) from it raises `badarg` and the rest of the table is never visited. Whether a `for` loop leaves the `dict`, `set` or `deque` it is walking alone — CPython's iterators over those check that the collection has not changed size since the loop began, so a body that removes from (or empties) the very collection the loop is walking makes the next step raise `RuntimeError: dictionary changed size during iteration` and the remaining items are never seen.

Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.

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.

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.

X3 · Exception handling5.0 / 10Adequate✓ Tool-verified

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, 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. (×37) — apps/openapi_scaffold/src/openapi_graphql_bridge.erl:558, apps/openapi_scaffold/src/openapi_parser.erl:181, apps/openapi_scaffold/src/openapi_playground.erl:591, …
  • `catch error:_` 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) — apps/openapi_scaffold/src/openapi_validator.erl:260, apps/openapi_scaffold/src/openapi_validator.erl:278, apps/openapi_scaffold/src/openapi_validator.erl:290

What to do

  • Swallowed exception (caught, then discarded)
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.

X5 · Nullable reference types2.0 / 10Critical✓ Tool-verified

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.

  • 0/2 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.
  • ~0.3 `!` null assertions per 1k TypeScript source lines — 9 assertion(s) across the 29134 source line(s) of the 82 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: apps/agent_web/frontend/src/services/CollaborationManager.ts (4), apps/agent_web/frontend/src/components/MCPOrchestrationEngine.tsx (1), REDACTED (1). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.

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 `?`).

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).

DimensionWCAG 2.2 A/AA criteriaCoverage
AC1 · Text alternatives1.1.1, 1.2.2, 1.2.5Partial signal
AC2 · Forms & labels1.3.1, 3.3.2, 4.1.2Partial signal
AC3 · Page structure1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2Partial signal
AC4 · Keyboard semantics2.1.1, 2.4.3Partial signal
AC5 · ARIA correctness4.1.2Partial signal
AC6 · Visual & motion safety1.4.3, 2.4.7Partial — literal CSS only
AC7 · A11y enforcementenforcement — no page criterionEnforcement posture (process)

Not statically assessed — these 40 Level A/AA criteria need runtime or manual evaluation (WCAG-EM): 1.2.1, 1.2.3, 1.2.4, 1.3.2, 1.3.3, 1.3.4, 1.3.5, 1.4.1, 1.4.2, 1.4.5, 1.4.10, 1.4.11, 1.4.12, 1.4.13, 2.1.2, 2.1.4, 2.2.2, 2.3.1, 2.4.4, 2.4.5, 2.4.6, 2.4.11, 2.5.1, 2.5.2, 2.5.3, 2.5.4, 2.5.7, 2.5.8, 3.1.2, 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.2.6, 3.3.1, 3.3.3, 3.3.4, 3.3.7, 3.3.8, 4.1.3.

Reference — by lens

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.

LensScoreRatingImpact
Code Health27%Weak — gated by D3, R3, R7, X5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture93%Adequate — gated by D26Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity82%StrongSolid.
Readiness21%Weak — gated by R4, R8, P1, P3, P7Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security69%Adequate — gated by D30Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Event-Driven61%AdequateAcceptable, with room to improve.
Event Sourcing74%StrongSolid.
Accessibility32%Weak — gated by AC1, AC2, AC4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance100%ExemplaryStrongest area.
Unscored — 2 check(s) recorded observations but carry no score

These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.

  • X10 Duplicated predicate — 5 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X31 Test-only surface in a production module — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 5 control(s) we could not find positive evidence for

These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.

  • C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 50 check(s) not relevant to this codebase

These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.

  • AX1 Captive dependencies — Not applicable: the BEAM has no dependency-injection container — state lives in processes, and no process is handed an instance whose lifetime another one scopes; this repository's Python imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
  • AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. Erlang processes share no mutable memory — state lives in a process's own mailbox — so there is no shared object to race on. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
  • AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX6 Interface segregation — no exported interface declares behaviour
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX8 Test isolation — no test/production split to check
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
  • C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • D10 Test Quality — ~17983 lines of test source are present (.erl) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
  • D11 Test Reliability — Test reliability not included — the .erl suite was found but not re-run
  • D16 Bus Factor — single-contributor repository — bus factor is not applicable
  • D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
  • D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Erlang, JavaScript, Python not measured.
  • D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
  • D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .erl, .py, .ts, .tsx, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D25 ADR Conformance — no ADRs to check
  • D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.erl), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
  • D32 Data Compliance (PII/GDPR) — 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.
  • D34 Knowledge Freshness — too few commits to judge knowledge freshness
  • D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
  • D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
  • D8 Code Coverage — Coverage not included — suite not readable by the collector
  • D9 Test Distribution — Test source is present (.erl) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
  • DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (577 value object(s))
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
  • GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
  • IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • P12 CI test-gate honesty — no CI workflow found
  • P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
  • P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (`rebar3 do eunit --cover, cover` (or covertool for Cobertura XML)) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
  • PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `erlperf:run`/`compare`/`benchmark`/`time` calls, a common_test `benchmark_data` event, `bench_*` functions in a `bench_*.erl` module where rebar.config installs rebar3_bench, or erlperf or rebar3_bench in a rebar.config, 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 applicable: Erlang and TypeScript/JavaScript runs on a garbage-collected runtime that gives a program no allocation-control idiom to choose on a hot path — no pools, stack allocation or value types — so allocation awareness is not something this code can be rated on.
  • R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
  • SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.

Critical — 71 finding(s)
D30 · Dependency Vulnerabilities · High CVE · ×15
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC4 · Keyboard semantics · Click handler on a non-interactive <div> · ×14
  • Click handler on a non-interactive <div> REDACTED:571 — 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> apps/agent_web/frontend/src/components/AgentList.tsx:25 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
  • Click handler on a non-interactive <div> apps/agent_web/frontend/src/components/AgentPillXL.tsx:95 — 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> apps/agent_web/frontend/src/components/AgentPillXL.tsx:129 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
  • Click handler on a non-interactive <div> apps/agent_web/frontend/src/components/ApiKeyManager.tsx:196 — 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> apps/agent_web/frontend/src/components/ChainOfThoughtVisualization.tsx:515 — 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> apps/agent_web/frontend/src/components/CrashMonitorDashboard.tsx:421 — 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> apps/agent_web/frontend/src/components/DiscoveryMeshDashboard.tsx:288 — A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}.
  • Click handler on a non-interactive <div> apps/agent_web/frontend/src/components/ErrorInterpretationPanel.tsx:327 — 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> apps/agent_web/frontend/src/components/FlameGraph.tsx:118 — 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> apps/agent_web/frontend/src/components/FleetManagementDashboard.tsx:440 — 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> apps/agent_web/frontend/src/components/MCPOrchestrationEngine.tsx:904 — 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> apps/agent_web/frontend/src/components/NetworkTopology.tsx:126 — 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> apps/agent_web/frontend/src/components/TokenHeatmap.tsx:136 — 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 · <label> that labels no control · ×11
  • <label> that labels no control apps/agent_web/frontend/src/components/FleetManagementDashboard.tsx:334 — This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control apps/agent_web/frontend/src/components/FleetManagementDashboard.tsx:345 — This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control apps/agent_web/frontend/src/components/InteractiveReasoningControls.tsx:240 — This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control apps/agent_web/frontend/src/components/InteractiveReasoningControls.tsx:252 — This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control apps/agent_web/frontend/src/components/InteractiveReasoningControls.tsx:315 — This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control apps/agent_web/frontend/src/components/InteractiveReasoningControls.tsx:338 — This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control apps/agent_web/frontend/src/components/InteractiveReasoningControls.tsx:350 — This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control apps/agent_web/frontend/src/components/InteractiveReasoningControls.tsx:363 — This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control apps/agent_web/frontend/src/components/InteractiveReasoningControls.tsx:383 — This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control apps/agent_web/frontend/src/components/InteractiveReasoningControls.tsx:422 — This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control apps/agent_web/frontend/src/components/InteractiveReasoningControls.tsx:445 — This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
AC4 · Keyboard semantics · Clickable element isn't keyboard-operable · ×6
  • Clickable element isn't keyboard-operable REDACTED:496 — The repo's own CSS styles .agent-item with `cursor: pointer`, so this <li> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Clickable element isn't keyboard-operable REDACTED:1331 — The repo's own CSS styles .node with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Clickable element isn't keyboard-operable REDACTED:1332 — The repo's own CSS styles .node with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Clickable element isn't keyboard-operable REDACTED:1333 — The repo's own CSS styles .node with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Clickable element isn't keyboard-operable REDACTED:1334 — The repo's own CSS styles .node with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Clickable element isn't keyboard-operable REDACTED:1335 — The repo's own CSS styles .node with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
AC2 · Forms & labels · <select> without a programmatic label · ×5
  • <select> without a programmatic label REDACTED:1018 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <select> without a programmatic label REDACTED:1030 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <select> without a programmatic label REDACTED:1062 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <select> without a programmatic label apps/agent_web/frontend/src/components/ChainOfThoughtVisualization.tsx:302 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <select> without a programmatic label apps/agent_web/frontend/src/components/ComprehensiveMCPManager.tsx:966 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC2 · Forms & labels · <button> with no accessible text · ×3
  • <button> with no accessible text apps/agent_web/frontend/src/components/AgentQuorumPanel.tsx:303 — 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 apps/agent_web/frontend/src/components/AgentQuorumPanel.tsx:309 — 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 apps/agent_web/frontend/src/components/ApiKeyNotification.tsx:96 — A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
AC2 · Forms & labels · <input> without a programmatic label · ×2
  • <input> without a programmatic label REDACTED:555 — 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 apps/agent_web/frontend/src/components/InteractiveReasoningControls.tsx:367 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
D28 · Secrets (history) · REDACTED · ×2
  • REDACTED
  • REDACTED
AC2 · Forms & labels · Custom control with no accessible name on <canvas> · ×1
  • Custom control with no accessible name on <canvas> apps/agent_web/frontend/src/components/ChainOfThoughtVisualization.tsx:331 — 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.
AC2 · Forms & labels · <textarea> without a programmatic label · ×1
  • <textarea> without a programmatic label apps/agent_web/frontend/src/components/ContextMenu.tsx:110 — 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 <canvas> · ×1
  • Click handler on a non-interactive <canvas> apps/agent_web/frontend/src/components/ChainOfThoughtVisualization.tsx:331 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
AC4 · Keyboard semantics · Click handler on a non-interactive <circle> · ×1
  • Click handler on a non-interactive <circle> apps/agent_web/frontend/src/components/InteractiveWidgets.tsx:150 — A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}.
AC4 · Keyboard semantics · Click handler on a non-interactive <path> · ×1
  • Click handler on a non-interactive <path> apps/agent_web/frontend/src/components/InteractiveWidgets.tsx:180 — A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}.
AC4 · Keyboard semantics · Hover-only interaction on <div> · ×1
  • Hover-only interaction on <div> apps/agent_web/frontend/src/components/OpStackBar.tsx:81 — This <div> 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.
AC4 · Keyboard semantics · Click handler on a non-interactive <img> · ×1
  • Click handler on a non-interactive <img> REDACTED:1054 — A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}.
AC4 · Keyboard semantics · Click handler on a non-interactive <li> · ×1
  • Click handler on a non-interactive <li> REDACTED:501 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
AX9 · CQS / query purity · Query handler writes persistent state on the read path · ×1
  • Query handler writes persistent state on the read path: openapi_ai_transform apps/openapi_scaffold/src/openapi_ai_transform.erl:85 — `openapi_ai_transform` has a `handle_call` query clause that reads a store and, on the not-found (cache-miss) branch, WRITES it — a get-or-create that mutates as a side effect of a read. A query must stay side-effect-free so reads are safe to retry, cache, and route to a read replica; move the lazy-init write into a command.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
ES1 · Fold determinism · Nondeterministic fold · ×1
  • Nondeterministic fold: agent_api_handler apps/agent_web/src/agent_api_handler.erl:306 — `agent_api_handler`'s event-replay reducer reads a wall clock / randomness / a peer process / persistence while reconstructing aggregate state — replaying the same events would rebuild DIFFERENT state each run. A fold must be a pure function of (state, event); stamp the timestamp/id into the event at raise-time and read it back in the fold.
R8 · Dependency Hygiene · Unlisted import 'highlight.js' · ×1
  • Unlisted import 'highlight.js' REDACTED:13 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'katex' · ×1
  • Unlisted import 'katex' REDACTED:12 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Serious — 1119 finding(s)
D3 · God Classes · TooManyFunctions · ×94
  • TooManyFunctions: distributed_consciousness_engine apps/agents/src/distributed_consciousness_engine.erl:12 — TooManyFunctions — 105 functions. The bar is 30 functions; this is 75 over it, 3.50× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
  • TooManyFunctions: quantum_runtime apps/agents/src/quantum_runtime.erl:3 — TooManyFunctions — 100 functions. The bar is 30 functions; this is 70 over it, 3.33× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
  • TooManyFunctions: time_travel_debugging apps/agents/src/time_travel_debugging.erl:4 — TooManyFunctions — 99 functions. The bar is 30 functions; this is 69 over it, 3.30× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
  • TooManyFunctions: cognitive_workflow_orchestrator apps/agents/src/cognitive_workflow_orchestrator.erl:4 — TooManyFunctions — 95 functions. The bar is 30 functions; this is 65 over it, 3.17× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
  • TooManyFunctions: evolutionary_supervision apps/agents/src/evolutionary_supervision.erl:4 — TooManyFunctions — 93 functions. The bar is 30 functions; this is 63 over it, 3.10× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
  • TooManyFunctions: neural_symbolic_reasoning_engine apps/agents/src/neural_symbolic_reasoning_engine.erl:4 — TooManyFunctions — 93 functions. The bar is 30 functions; this is 63 over it, 3.10× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
  • TooManyFunctions: self_reflection_system apps/agents/src/self_reflection_system.erl:1 — TooManyFunctions — 92 functions. The bar is 30 functions; this is 62 over it, 3.07× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
  • TooManyFunctions: dimensional_phase_shift_engine apps/agents/src/dimensional_phase_shift_engine.erl:5 — TooManyFunctions — 88 functions. The bar is 30 functions; this is 58 over it, 2.93× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
  • TooManyFunctions: self_modifying_agent_engine apps/agents/src/self_modifying_agent_engine.erl:4 — TooManyFunctions — 87 functions. The bar is 30 functions; this is 57 over it, 2.90× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
  • TooManyFunctions: swarm_intelligence_engine apps/agents/src/swarm_intelligence_engine.erl:4 — TooManyFunctions — 87 functions. The bar is 30 functions; this is 57 over it, 2.90× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
  • TooManyFunctions: quantum_digital_twins_engine apps/agents/src/quantum_digital_twins_engine.erl:5 — TooManyFunctions — 86 functions. The bar is 30 functions; this is 56 over it, 2.87× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
  • TooManyFunctions: absolute_impossibility_orchestrator apps/agent_web/src/absolute_impossibility_orchestrator.erl:1 — TooManyFunctions — 85 functions. The bar is 30 functions; this is 55 over it, 2.83× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
  • TooManyFunctions: concept_creation_engine apps/agent_web/src/concept_creation_engine.erl:1 — TooManyFunctions — 85 functions. The bar is 30 functions; this is 55 over it, 2.83× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
  • TooManyFunctions: paradox_resolution_matrix apps/agent_web/src/paradox_resolution_matrix.erl:1 — TooManyFunctions — 85 functions. The bar is 30 functions; this is 55 over it, 2.83× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
  • TooManyFunctions: self_contradiction_synthesis_protocol apps/agent_web/src/self_contradiction_synthesis_protocol.erl:1 — TooManyFunctions — 85 functions. The bar is 30 functions; this is 55 over it, 2.83× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
  • TooManyFunctions: void_architecture_system apps/agent_web/src/void_architecture_system.erl:1 — TooManyFunctions — 85 functions. The bar is 30 functions; this is 55 over it, 2.83× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
  • TooManyFunctions: autonomous_knowledge_ingestion apps/agents/src/autonomous_knowledge_ingestion.erl:3 — TooManyFunctions — 85 functions. The bar is 30 functions; this is 55 over it, 2.83× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
  • TooManyFunctions: distributed_consensus_engine apps/agents/src/distributed_consensus_engine.erl:4 — TooManyFunctions — 85 functions. The bar is 30 functions; this is 55 over it, 2.83× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
  • TooManyFunctions: temporal_meta_analyzer apps/agents/src/temporal_meta_analyzer.erl:8 — TooManyFunctions — 85 functions. The bar is 30 functions; this is 55 over it, 2.83× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
  • TooManyFunctions: meta_reality_generator apps/agent_web/src/meta_reality_generator.erl:1 — TooManyFunctions — 84 functions. The bar is 30 functions; this is 54 over it, 2.80× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
  • TooManyFunctions: continuous_self_monitor apps/agent_web/src/continuous_self_monitor.erl:8 — TooManyFunctions — 83 functions. The bar is 30 functions; this is 53 over it, 2.77× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
  • TooManyFunctions: hierarchical_task_executor apps/agents/src/hierarchical_task_executor.erl:4 — TooManyFunctions — 83 functions. The bar is 30 functions; this is 53 over it, 2.77× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
  • TooManyFunctions: expert_agent_selector apps/agents/src/expert_agent_selector.erl:3 — TooManyFunctions — 79 functions. The bar is 30 functions; this is 49 over it, 2.63× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
  • TooManyFunctions: reflection_mechanism apps/agents/src/reflection_mechanism.erl:1 — TooManyFunctions — 78 functions. The bar is 30 functions; this is 48 over it, 2.60× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
  • TooManyFunctions: quantum_process_network apps/agents/src/quantum_process_network.erl:4 — TooManyFunctions — 77 functions. The bar is 30 functions; this is 47 over it, 2.57× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
  • + 69 more in this group — see findings.md.
D3 · God Classes · FileTooLong · ×74
  • FileTooLong: src/agent_tools.erl apps/agents/src/agent_tools.erl — FileTooLong — 2747 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 83 functions. The bar is 500 significant lines; this is 2247 over it, 5.49× the bar. In this language a module is exactly one source file, so its length cannot be moved into sibling files of the same module. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no one module has to be read whole to change one of them.
  • FileTooLong: src/agent_instance.erl apps/agents/src/agent_instance.erl — FileTooLong — 1611 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 99 functions. The bar is 500 significant lines; this is 1111 over it, 3.22× the bar. In this language a module is exactly one source file, so its length cannot be moved into sibling files of the same module. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no one module has to be read whole to change one of them.
  • FileTooLong: REDACTED REDACTED — FileTooLong — 1268 significant lines (blank, comment-only and punctuation-only lines excluded), about 66% of them inside a single declaration: AdvancedMCPDashboard (157-1219). The bar is 500 significant lines; this is 768 over it, 2.54× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: src/ai_performance_optimizer.erl apps/agent_web/src/ai_performance_optimizer.erl — FileTooLong — 1103 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 103 functions. The bar is 500 significant lines; this is 603 over it, 2.21× the bar. In this language a module is exactly one source file, so its length cannot be moved into sibling files of the same module. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no one module has to be read whole to change one of them.
  • FileTooLong: src/specialized_agent_templates.erl apps/agents/src/specialized_agent_templates.erl — FileTooLong — 958 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 458 over it, 1.92× the bar. In this language a module is exactly one source file, so its length cannot be moved into sibling files of the same module. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no one module has to be read whole to change one of them.
  • FileTooLong: REDACTED REDACTED — FileTooLong — 922 significant lines (blank, comment-only and punctuation-only lines excluded), about 68% of them inside a single declaration: SimpleAdvancedChat (384-1226). The bar is 500 significant lines; this is 422 over it, 1.84× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: src/emergent_swarm_intelligence.erl apps/agents/src/emergent_swarm_intelligence.erl — FileTooLong — 901 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 157 functions. The bar is 500 significant lines; this is 401 over it, 1.80× the bar. In this language a module is exactly one source file, so its length cannot be moved into sibling files of the same module. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no one module has to be read whole to change one of them.
  • FileTooLong: components/MCPOrchestrationEngine.tsx apps/agent_web/frontend/src/components/MCPOrchestrationEngine.tsx — FileTooLong — 891 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 391 over it, 1.78× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: components/ComprehensiveMCPManager.tsx apps/agent_web/frontend/src/components/ComprehensiveMCPManager.tsx — FileTooLong — 883 significant lines (blank, comment-only and punctuation-only lines excluded), about 61% of them inside a single declaration: ComprehensiveMCPManager (48-718). The bar is 500 significant lines; this is 383 over it, 1.77× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: src/openapi_advanced_codegen.erl apps/openapi_scaffold/src/openapi_advanced_codegen.erl — FileTooLong — 810 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 65 functions. The bar is 500 significant lines; this is 310 over it, 1.62× the bar. In this language a module is exactly one source file, so its length cannot be moved into sibling files of the same module. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no one module has to be read whole to change one of them.
  • FileTooLong: components/UltraAdvancedDashboard.tsx apps/agent_web/frontend/src/components/UltraAdvancedDashboard.tsx — FileTooLong — 777 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 277 over it, 1.55× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: src/distributed_consensus_tracker.erl apps/agent_web/src/distributed_consensus_tracker.erl — FileTooLong — 770 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 68 functions. The bar is 500 significant lines; this is 270 over it, 1.54× the bar. In this language a module is exactly one source file, so its length cannot be moved into sibling files of the same module. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no one module has to be read whole to change one of them.
  • FileTooLong: src/mcp_manager.erl apps/agent_web/src/mcp_manager.erl — FileTooLong — 764 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 59 functions. The bar is 500 significant lines; this is 264 over it, 1.53× the bar. In this language a module is exactly one source file, so its length cannot be moved into sibling files of the same module. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no one module has to be read whole to change one of them.
  • FileTooLong: src/mcp_client_v2.erl apps/agent_web/src/mcp_client_v2.erl — FileTooLong — 756 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 40 functions. The bar is 500 significant lines; this is 256 over it, 1.51× the bar. In this language a module is exactly one source file, so its length cannot be moved into sibling files of the same module. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no one module has to be read whole to change one of them.
  • FileTooLong: components/ModelTypeEditor.tsx apps/agent_web/frontend/src/components/ModelTypeEditor.tsx — FileTooLong — 749 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: ModelTypeEditor (82-896). The bar is 500 significant lines; this is 249 over it, 1.50× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: src/specialized_agent_factory.erl apps/agents/src/specialized_agent_factory.erl — FileTooLong — 730 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 31 functions. The bar is 500 significant lines; this is 230 over it, 1.46× the bar. In this language a module is exactly one source file, so its length cannot be moved into sibling files of the same module. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no one module has to be read whole to change one of them.
  • FileTooLong: src/openapi_playground.erl apps/openapi_scaffold/src/openapi_playground.erl — FileTooLong — 727 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 77 functions. The bar is 500 significant lines; this is 227 over it, 1.45× the bar. In this language a module is exactly one source file, so its length cannot be moved into sibling files of the same module. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no one module has to be read whole to change one of them.
  • FileTooLong: src/super_agent_tools.erl apps/agents/src/super_agent_tools.erl — FileTooLong — 707 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 93 functions. The bar is 500 significant lines; this is 207 over it, 1.41× the bar. In this language a module is exactly one source file, so its length cannot be moved into sibling files of the same module. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no one module has to be read whole to change one of them.
  • FileTooLong: src/openapi_security.erl apps/openapi_scaffold/src/openapi_security.erl — FileTooLong — 707 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 76 functions. The bar is 500 significant lines; this is 207 over it, 1.41× the bar. In this language a module is exactly one source file, so its length cannot be moved into sibling files of the same module. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no one module has to be read whole to change one of them.
  • FileTooLong: src/bulk_operations_handler.erl apps/agent_web/src/bulk_operations_handler.erl — FileTooLong — 692 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 41 functions. The bar is 500 significant lines; this is 192 over it, 1.38× the bar. In this language a module is exactly one source file, so its length cannot be moved into sibling files of the same module. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no one module has to be read whole to change one of them.
  • FileTooLong: src/jina_tools.erl apps/agents/src/jina_tools.erl — FileTooLong — 690 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 190 over it, 1.38× the bar. In this language a module is exactly one source file, so its length cannot be moved into sibling files of the same module. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no one module has to be read whole to change one of them.
  • FileTooLong: src/mcp_server.erl apps/agent_web/src/mcp_server.erl — FileTooLong — 683 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 183 over it, 1.37× the bar. In this language a module is exactly one source file, so its length cannot be moved into sibling files of the same module. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no one module has to be read whole to change one of them.
  • FileTooLong: src/active_exploration_engine.erl apps/agents/src/active_exploration_engine.erl — FileTooLong — 671 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 178 functions. The bar is 500 significant lines; this is 171 over it, 1.34× the bar. In this language a module is exactly one source file, so its length cannot be moved into sibling files of the same module. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no one module has to be read whole to change one of them.
  • FileTooLong: src/agent.erl apps/agents/src/agent.erl — FileTooLong — 660 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 56 functions. The bar is 500 significant lines; this is 160 over it, 1.32× the bar. In this language a module is exactly one source file, so its length cannot be moved into sibling files of the same module. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no one module has to be read whole to change one of them.
  • FileTooLong: src/environmental_learning_engine.erl apps/agents/src/environmental_learning_engine.erl — FileTooLong — 645 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 148 functions. The bar is 500 significant lines; this is 145 over it, 1.29× the bar. In this language a module is exactly one source file, so its length cannot be moved into sibling files of the same module. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no one module has to be read whole to change one of them.
  • + 49 more in this group — see findings.md.
D3 · God Classes · FunctionTooLong · ×56
  • FunctionTooLong: AdvancedMCPDashboard.AdvancedMCPDashboard REDACTED:157 — FunctionTooLong — AdvancedMCPDashboard runs 832 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 732 over it, 8.32× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: ModelTypeEditor.ModelTypeEditor apps/agent_web/frontend/src/components/ModelTypeEditor.tsx:82 — FunctionTooLong — ModelTypeEditor runs 678 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 578 over it, 6.78× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: SimpleAdvancedChat.SimpleAdvancedChat REDACTED:384 — FunctionTooLong — SimpleAdvancedChat runs 628 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 528 over it, 6.28× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: ComprehensiveMCPManager.ComprehensiveMCPManager apps/agent_web/frontend/src/components/ComprehensiveMCPManager.tsx:48 — FunctionTooLong — ComprehensiveMCPManager runs 539 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 439 over it, 5.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.
  • FunctionTooLong: App.App apps/agent_web/frontend/src/App.tsx:55 — FunctionTooLong — App runs 528 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 428 over it, 5.28× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: CrashMonitorDashboard.CrashMonitorDashboard apps/agent_web/frontend/src/components/CrashMonitorDashboard.tsx:86 — FunctionTooLong — CrashMonitorDashboard runs 491 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 391 over it, 4.91× 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: DiscoveryMeshDashboard.DiscoveryMeshDashboard apps/agent_web/frontend/src/components/DiscoveryMeshDashboard.tsx:55 — FunctionTooLong — DiscoveryMeshDashboard runs 476 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 376 over it, 4.76× 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: UltimatePerformanceDashboard.UltimatePerformanceDashboard apps/agent_web/frontend/src/components/UltimatePerformanceDashboard.tsx:97 — FunctionTooLong — UltimatePerformanceDashboard runs 472 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 372 over it, 4.72× 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: ModelConfiguration.ModelConfiguration apps/agent_web/frontend/src/components/ModelConfiguration.tsx:65 — FunctionTooLong — ModelConfiguration runs 459 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 359 over it, 4.59× 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: AdvancedStructuredOutputsManager.AdvancedStructuredOutputsManager apps/agent_web/frontend/src/components/AdvancedStructuredOutputsManager.tsx:62 — FunctionTooLong — AdvancedStructuredOutputsManager runs 448 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 348 over it, 4.48× 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: QuantumConsciousnessInterface.QuantumConsciousnessInterface apps/agent_web/frontend/src/components/QuantumConsciousnessInterface.tsx:59 — FunctionTooLong — QuantumConsciousnessInterface runs 448 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 348 over it, 4.48× 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: AdaptiveAIInterface.AdaptiveAIInterface apps/agent_web/frontend/src/components/AdaptiveAIInterface.tsx:46 — FunctionTooLong — AdaptiveAIInterface runs 429 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 329 over it, 4.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: Timeline.Timeline apps/agent_web/frontend/src/components/Timeline.tsx:59 — FunctionTooLong — Timeline runs 401 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 301 over it, 4.01× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: UltraAdvancedDashboard.UltraAdvancedDashboard apps/agent_web/frontend/src/components/UltraAdvancedDashboard.tsx:477 — FunctionTooLong — UltraAdvancedDashboard runs 399 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 299 over it, 3.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: ToolRegistry.ToolRegistry apps/agent_web/frontend/src/components/ToolRegistry.tsx:69 — FunctionTooLong — ToolRegistry runs 396 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 296 over it, 3.96× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: SystemMonitoringDashboard.SystemMonitoringDashboard apps/agent_web/frontend/src/components/SystemMonitoringDashboard.tsx:65 — FunctionTooLong — SystemMonitoringDashboard runs 394 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 294 over it, 3.94× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: ErrorInterpretationPanel.ErrorInterpretationPanel apps/agent_web/frontend/src/components/ErrorInterpretationPanel.tsx:55 — FunctionTooLong — ErrorInterpretationPanel runs 382 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 282 over it, 3.82× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: MCPOrchestrationEngine.MCPOrchestrationEngine apps/agent_web/frontend/src/components/MCPOrchestrationEngine.tsx:165 — FunctionTooLong — MCPOrchestrationEngine runs 367 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 267 over it, 3.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: InteractiveReasoningControls.InteractiveReasoningControls apps/agent_web/frontend/src/components/InteractiveReasoningControls.tsx:53 — FunctionTooLong — InteractiveReasoningControls runs 353 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 253 over it, 3.53× 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: FleetManagementDashboard.FleetManagementDashboard apps/agent_web/frontend/src/components/FleetManagementDashboard.tsx:53 — FunctionTooLong — FleetManagementDashboard runs 350 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 250 over it, 3.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: PipedreamConnectionManager.PipedreamConnectionManager apps/agent_web/frontend/src/components/PipedreamConnectionManager.tsx:60 — FunctionTooLong — PipedreamConnectionManager runs 327 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 227 over it, 3.27× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: ChainOfThoughtVisualization.ChainOfThoughtVisualization apps/agent_web/frontend/src/components/ChainOfThoughtVisualization.tsx:52 — FunctionTooLong — ChainOfThoughtVisualization runs 321 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 221 over it, 3.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: OAuthManager.OAuthManager apps/agent_web/frontend/src/components/OAuthManager.tsx:92 — FunctionTooLong — OAuthManager runs 307 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 207 over it, 3.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: ClaudeCLI.ClaudeCLI apps/agent_web/frontend/src/components/ClaudeCLI.tsx:31 — FunctionTooLong — ClaudeCLI runs 294 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 194 over it, 2.94× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: SimpleAdvancedChat.detectContentFormat REDACTED:47 — FunctionTooLong — detectContentFormat runs 255 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 155 over it, 2.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.
  • + 31 more in this group — see findings.md.
ED1 · Handler temporal coupling · Handler temporal coupling · ×40
  • Handler temporal coupling: distributed_error_coordinator clause `handle_call/3#90` apps/agent_web/src/distributed_error_coordinator.erl:96 — `distributed_error_coordinator` clause `handle_call/3#90` blocks on a hand-rolled `Pid ! Req, receive Resp` rendezvous awaiting a peer's reply while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, reply asynchronously (send-and-continue), or run the round-trip in a throwaway spawned process.
  • Handler temporal coupling: embedding_integration clause `handle_call/3#86` apps/agent_web/src/embedding_integration.erl:410 — `embedding_integration` clause `handle_call/3#86` blocks the process on a synchronous outbound I/O client call (a remote HTTP request, a socket receive, or a blocking pool checkout) awaited inline while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, issue the request off the hot path — reply asynchronously and do the I/O in a throwaway spawned worker (or use the async client API), so the process keeps serving its mailbox.
  • Handler temporal coupling: embedding_integration clause `handle_call/3#117` apps/agent_web/src/embedding_integration.erl:410 — `embedding_integration` clause `handle_call/3#117` blocks the process on a synchronous outbound I/O client call (a remote HTTP request, a socket receive, or a blocking pool checkout) awaited inline while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, issue the request off the hot path — reply asynchronously and do the I/O in a throwaway spawned worker (or use the async client API), so the process keeps serving its mailbox.
  • Handler temporal coupling: embedding_integration clause `handle_call/3#254` apps/agent_web/src/embedding_integration.erl:259 — `embedding_integration` clause `handle_call/3#254` makes a synchronous `gen_server`/`gen_statem:call` round-trip to a peer process while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, react by casting a follow-up message (fire-and-forget), or resolve the needed state locally.
  • Handler temporal coupling: mcp_client_v2 clause `handle_call/3#105` apps/agent_web/src/mcp_client_v2.erl:327 — `mcp_client_v2` clause `handle_call/3#105` blocks the process on a synchronous outbound I/O client call (a remote HTTP request, a socket receive, or a blocking pool checkout) awaited inline while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, issue the request off the hot path — reply asynchronously and do the I/O in a throwaway spawned worker (or use the async client API), so the process keeps serving its mailbox.
  • Handler temporal coupling: mcp_client_v2 clause `handle_call/3#105` apps/agent_web/src/mcp_client_v2.erl:757 — `mcp_client_v2` clause `handle_call/3#105` blocks the process on a synchronous outbound I/O client call (a remote HTTP request, a socket receive, or a blocking pool checkout) awaited inline while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, issue the request off the hot path — reply asynchronously and do the I/O in a throwaway spawned worker (or use the async client API), so the process keeps serving its mailbox.
  • Handler temporal coupling: mcp_client_v2 clause `handle_call/3#208` apps/agent_web/src/mcp_client_v2.erl:757 — `mcp_client_v2` clause `handle_call/3#208` blocks the process on a synchronous outbound I/O client call (a remote HTTP request, a socket receive, or a blocking pool checkout) awaited inline while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, issue the request off the hot path — reply asynchronously and do the I/O in a throwaway spawned worker (or use the async client API), so the process keeps serving its mailbox.
  • Handler temporal coupling: mcp_client_v2 clause `handle_cast/2#225` apps/agent_web/src/mcp_client_v2.erl:757 — `mcp_client_v2` clause `handle_cast/2#225` blocks the process on a synchronous outbound I/O client call (a remote HTTP request, a socket receive, or a blocking pool checkout) awaited inline while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, issue the request off the hot path — reply asynchronously and do the I/O in a throwaway spawned worker (or use the async client API), so the process keeps serving its mailbox.
  • Handler temporal coupling: mcp_client_v2 clause `handle_info/2#236` apps/agent_web/src/mcp_client_v2.erl:757 — `mcp_client_v2` clause `handle_info/2#236` blocks the process on a synchronous outbound I/O client call (a remote HTTP request, a socket receive, or a blocking pool checkout) awaited inline while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, issue the request off the hot path — reply asynchronously and do the I/O in a throwaway spawned worker (or use the async client API), so the process keeps serving its mailbox.
  • Handler temporal coupling: mcp_client_v2 clause `handle_info/2#240` apps/agent_web/src/mcp_client_v2.erl:757 — `mcp_client_v2` clause `handle_info/2#240` blocks the process on a synchronous outbound I/O client call (a remote HTTP request, a socket receive, or a blocking pool checkout) awaited inline while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, issue the request off the hot path — reply asynchronously and do the I/O in a throwaway spawned worker (or use the async client API), so the process keeps serving its mailbox.
  • Handler temporal coupling: mcp_client_v2 clause `handle_info/2#244` apps/agent_web/src/mcp_client_v2.erl:757 — `mcp_client_v2` clause `handle_info/2#244` blocks the process on a synchronous outbound I/O client call (a remote HTTP request, a socket receive, or a blocking pool checkout) awaited inline while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, issue the request off the hot path — reply asynchronously and do the I/O in a throwaway spawned worker (or use the async client API), so the process keeps serving its mailbox.
  • Handler temporal coupling: mcp_client_v2 clause `handle_info/2#276` apps/agent_web/src/mcp_client_v2.erl:757 — `mcp_client_v2` clause `handle_info/2#276` blocks the process on a synchronous outbound I/O client call (a remote HTTP request, a socket receive, or a blocking pool checkout) awaited inline while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, issue the request off the hot path — reply asynchronously and do the I/O in a throwaway spawned worker (or use the async client API), so the process keeps serving its mailbox.
  • Handler temporal coupling: mcp_client_v2 clause `handle_websocket_message/2#520` apps/agent_web/src/mcp_client_v2.erl:757 — `mcp_client_v2` clause `handle_websocket_message/2#520` blocks the process on a synchronous outbound I/O client call (a remote HTTP request, a socket receive, or a blocking pool checkout) awaited inline while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, issue the request off the hot path — reply asynchronously and do the I/O in a throwaway spawned worker (or use the async client API), so the process keeps serving its mailbox.
  • Handler temporal coupling: mcp_client_v2 clause `handle_sse_data/2#530` apps/agent_web/src/mcp_client_v2.erl:757 — `mcp_client_v2` clause `handle_sse_data/2#530` blocks the process on a synchronous outbound I/O client call (a remote HTTP request, a socket receive, or a blocking pool checkout) awaited inline while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, issue the request off the hot path — reply asynchronously and do the I/O in a throwaway spawned worker (or use the async client API), so the process keeps serving its mailbox.
  • Handler temporal coupling: mcp_client_v2 clause `handle_response/3#622` apps/agent_web/src/mcp_client_v2.erl:757 — `mcp_client_v2` clause `handle_response/3#622` blocks the process on a synchronous outbound I/O client call (a remote HTTP request, a socket receive, or a blocking pool checkout) awaited inline while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, issue the request off the hot path — reply asynchronously and do the I/O in a throwaway spawned worker (or use the async client API), so the process keeps serving its mailbox.
  • Handler temporal coupling: mcp_github_registry_updater clause `handle_info/2#94` apps/agent_web/src/mcp_github_registry_updater.erl:161 — `mcp_github_registry_updater` clause `handle_info/2#94` blocks the process on a synchronous outbound I/O client call (a remote HTTP request, a socket receive, or a blocking pool checkout) awaited inline while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, issue the request off the hot path — reply asynchronously and do the I/O in a throwaway spawned worker (or use the async client API), so the process keeps serving its mailbox.
  • Handler temporal coupling: mcp_oauth_client clause `handle_cast/2#126` apps/agent_web/src/mcp_oauth_client.erl:269 — `mcp_oauth_client` clause `handle_cast/2#126` blocks the process on a synchronous outbound I/O client call (a remote HTTP request, a socket receive, or a blocking pool checkout) awaited inline while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, issue the request off the hot path — reply asynchronously and do the I/O in a throwaway spawned worker (or use the async client API), so the process keeps serving its mailbox.
  • Handler temporal coupling: mcp_oauth_client clause `handle_call/3#60` apps/agent_web/src/mcp_oauth_client.erl:300 — `mcp_oauth_client` clause `handle_call/3#60` blocks the process on a synchronous outbound I/O client call (a remote HTTP request, a socket receive, or a blocking pool checkout) awaited inline while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, issue the request off the hot path — reply asynchronously and do the I/O in a throwaway spawned worker (or use the async client API), so the process keeps serving its mailbox.
  • Handler temporal coupling: mcp_oauth_client clause `handle_call/3#89` apps/agent_web/src/mcp_oauth_client.erl:300 — `mcp_oauth_client` clause `handle_call/3#89` blocks the process on a synchronous outbound I/O client call (a remote HTTP request, a socket receive, or a blocking pool checkout) awaited inline while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, issue the request off the hot path — reply asynchronously and do the I/O in a throwaway spawned worker (or use the async client API), so the process keeps serving its mailbox.
  • Handler temporal coupling: mcp_oauth_client clause `handle_token_refresh/3#206` apps/agent_web/src/mcp_oauth_client.erl:300 — `mcp_oauth_client` clause `handle_token_refresh/3#206` blocks the process on a synchronous outbound I/O client call (a remote HTTP request, a socket receive, or a blocking pool checkout) awaited inline while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, issue the request off the hot path — reply asynchronously and do the I/O in a throwaway spawned worker (or use the async client API), so the process keeps serving its mailbox.
  • Handler temporal coupling: mcp_oauth_integration clause `handle_oauth_popup_callback/3#153` apps/agent_web/src/mcp_oauth_integration.erl:217 — `mcp_oauth_integration` clause `handle_oauth_popup_callback/3#153` blocks the process on a synchronous outbound I/O client call (a remote HTTP request, a socket receive, or a blocking pool checkout) awaited inline while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, issue the request off the hot path — reply asynchronously and do the I/O in a throwaway spawned worker (or use the async client API), so the process keeps serving its mailbox.
  • Handler temporal coupling: oauth_handler clause `handle_request/4#86` apps/agent_web/src/oauth_handler.erl:272 — `oauth_handler` clause `handle_request/4#86` blocks the process on a synchronous outbound I/O client call (a remote HTTP request, a socket receive, or a blocking pool checkout) awaited inline while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, issue the request off the hot path — reply asynchronously and do the I/O in a throwaway spawned worker (or use the async client API), so the process keeps serving its mailbox.
  • Handler temporal coupling: oauth_handler clause `handle_oauth_callback/3#135` apps/agent_web/src/oauth_handler.erl:272 — `oauth_handler` clause `handle_oauth_callback/3#135` blocks the process on a synchronous outbound I/O client call (a remote HTTP request, a socket receive, or a blocking pool checkout) awaited inline while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, issue the request off the hot path — reply asynchronously and do the I/O in a throwaway spawned worker (or use the async client API), so the process keeps serving its mailbox.
  • Handler temporal coupling: oauth_manager clause `handle_call/3#197` apps/agent_web/src/oauth_manager.erl:202 — `oauth_manager` clause `handle_call/3#197` makes a synchronous `gen_server`/`gen_statem:call` round-trip to a peer process while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, react by casting a follow-up message (fire-and-forget), or resolve the needed state locally.
  • Handler temporal coupling: openapi_fetcher clause `handle_call/3#70` apps/agent_web/src/openapi_fetcher.erl:164 — `openapi_fetcher` clause `handle_call/3#70` blocks the process on a synchronous outbound I/O client call (a remote HTTP request, a socket receive, or a blocking pool checkout) awaited inline while handling a message — the process is blocked (holding its mailbox) until a peer replies or the sleep elapses. That couples this handler in real time to another process being up and fast, and a mutual call can DEADLOCK. To decouple, issue the request off the hot path — reply asynchronously and do the I/O in a throwaway spawned worker (or use the async client API), so the process keeps serving its mailbox.
  • + 15 more in this group — see findings.md.
X24 · Document value interpolated into markup unescaped · Untrusted text written into markup unescaped · ×40
  • Untrusted text written into markup unescaped apps/agent_web/frontend/src/utils/sanitize.ts:22 — `html` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped REDACTED:502 — `agent.id` is text this program did not author, and it is written into a script or style context through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. A script or style context needs its own escaping (or a JSON serialiser that escapes `<`); better, pass the value through a data attribute.
  • Untrusted text written into markup unescaped REDACTED:504 — `agent.type` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped REDACTED:958 — `data.system.node` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped REDACTED:959 — `this.formatBytes(data.system.total_memory)` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped REDACTED:960 — `data.system.process_count` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped REDACTED:961 — `data.system.schedulers` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped REDACTED:979 — `agent.meta.name||'Unnamed'` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped REDACTED:980 — `String(agent.id).substring(0,8)` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped REDACTED:981 — `agent.status` is text this program did not author, and it is written into a quoted attribute value through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped REDACTED:982 — `this.formatBytes(agent.memory)` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped REDACTED:983 — `agent.message_queue` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped REDACTED:984 — `agent.id` is text this program did not author, and it is written into a script or style context through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. A script or style context needs its own escaping (or a JSON serialiser that escapes `<`); better, pass the value through a data attribute.
  • Untrusted text written into markup unescaped REDACTED:1021 — `t.name` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped REDACTED:1022 — `t.description` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped REDACTED:1023 — `t.id` is text this program did not author, and it is written into a script or style context through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. A script or style context needs its own escaping (or a JSON serialiser that escapes `<`); better, pass the value through a data attribute.
  • Untrusted text written into markup unescaped REDACTED:1048 — `String(agentId).substring(0,8)` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped REDACTED:1051 — `JSON.stringify(data.agent_state,null,2)` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped REDACTED:1054 — `JSON.stringify(data.performance,null,2)` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped REDACTED:1057 — `JSON.stringify(data.process_info,null,2)` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped REDACTED:1252 — `activity.type` is text this program did not author, and it is written into a quoted attribute value through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped REDACTED:1254 — `activity.title` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped REDACTED:1255 — `activity.description` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped REDACTED:1256 — `new Date().toLocaleTimeString()` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped REDACTED:1261 — `activityHtml+feed.innerHTML` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • + 15 more in this group — see findings.md.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×40
  • Swallowed exception (caught, then discarded) apps/openapi_scaffold/src/openapi_graphql_bridge.erl:558 — `catch _:_` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) apps/openapi_scaffold/src/openapi_parser.erl:181 — `catch _:_` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) apps/openapi_scaffold/src/openapi_playground.erl:591 — `catch _:_` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) apps/openapi_scaffold/src/openapi_validator.erl:260 — `catch error:_` 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) apps/openapi_scaffold/src/openapi_validator.erl:278 — `catch error:_` 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) apps/openapi_scaffold/src/openapi_validator.erl:290 — `catch error:_` 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) apps/openai/src/anthropic_client.erl:304 — `catch _:_` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) apps/openai/src/anthropic_client.erl:315 — `catch _:_` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) apps/openai/src/openai_config.erl:171 — `catch _:_` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) apps/openai/src/openai_rate_limiter.erl:191 — `catch _:_` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) apps/openai/src/openai_rate_limiter.erl:196 — `catch _:_` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) apps/openai/src/openai_rate_limiter.erl:201 — `catch _:_` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) apps/agents/src/agent.erl:621 — `catch _:_` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) apps/agents/src/agent.erl:637 — `catch _:_` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) apps/agents/src/agent.erl:650 — `catch _:_` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) apps/agents/src/agent.erl:960 — `catch _:_` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) apps/agents/src/agent_instance.erl:1071 — `catch _:_` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) apps/agents/src/agent_instance.erl:1915 — `catch _:_` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) apps/agents/src/agent_instance.erl:2048 — `catch _:_` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) apps/agents/src/agent_tools.erl:196 — `catch _:_` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) apps/agents/src/agent_tools.erl:213 — `catch _:_` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) apps/agents/src/agent_tools.erl:236 — `catch _:_` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) apps/agents/src/agent_tools.erl:2183 — `catch _:_` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) apps/agents/src/agent_tools.erl:2258 — `catch _:_` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) apps/agents/src/agent_tools.erl:2307 — `catch _:_` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • + 15 more in this group — see findings.md.
X2 · Cancellation propagation · Async function without AbortSignal · ×39
  • Async function without AbortSignal: loadAgents REDACTED:476 — `loadAgents` 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: createAgent REDACTED:659 — `createAgent` 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: runExample REDACTED:709 — `runExample` 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: sendSimpleMessage REDACTED:771 — `sendSimpleMessage` 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: loadAnalytics REDACTED:990 — `loadAnalytics` 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: viewAgentDetails REDACTED:1031 — `viewAgentDetails` 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: createFromTemplate REDACTED:1065 — `createFromTemplate` 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: stopAgent REDACTED:1393 — `stopAgent` 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: loadKnowledgeDomains REDACTED:1640 — `loadKnowledgeDomains` 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: loadDomainInfo REDACTED:1695 — `loadDomainInfo` 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: loadKnowledgeStatus REDACTED:1732 — `loadKnowledgeStatus` 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: discoverNewDomains REDACTED:1772 — `discoverNewDomains` 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: startIngestion REDACTED:1835 — `startIngestion` 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: loadDomainsForSearch REDACTED:1910 — `loadDomainsForSearch` 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: performSearch REDACTED:1926 — `performSearch` 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: viewDomainContents REDACTED:2007 — `viewDomainContents` 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: loadSystemMetrics apps/agent_web/frontend/src/App.tsx:131 — `loadSystemMetrics` 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: logButtonClick apps/agent_web/frontend/src/App.tsx:154 — `logButtonClick` 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: logError apps/agent_web/frontend/src/App.tsx:189 — `logError` 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: loadInitialAgents apps/agent_web/frontend/src/hooks/useAgents.tsx:32 — `loadInitialAgents` 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: refreshAgents apps/agent_web/frontend/src/hooks/useAgents.tsx:167 — `refreshAgents` 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: createAgent apps/agent_web/frontend/src/hooks/useAgents.tsx:177 — `createAgent` 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: deleteAgent apps/agent_web/frontend/src/hooks/useAgents.tsx:196 — `deleteAgent` 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: checkServerHealth REDACTED:252 — `checkServerHealth` 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: loadApiKeyStatus apps/agent_web/frontend/src/components/ApiKeyManager.tsx:69 — `loadApiKeyStatus` 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 })`.
  • + 14 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×35
  • Duplicated block (5 lines × 2) apps/agent_web/src/consciousness_bridge_api_handler.erl:60 — apps/agent_web/src/consciousness_bridge_api_handler.erl:60-64 | apps/agent_web/src/consciousness_bridge_api_handler.erl:74-78 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (5 lines × 2) apps/agent_web/src/consciousness_bridge_api_handler.erl:65 — apps/agent_web/src/consciousness_bridge_api_handler.erl:65-69 | apps/agent_web/src/consciousness_bridge_api_handler.erl:79-83 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (5 lines × 2) apps/agent_web/src/conversation_handler.erl:324 — apps/agent_web/src/conversation_handler.erl:324-328 | apps/agent_web/src/conversation_initializer.erl:91-95 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (5 lines × 2) apps/agent_web/src/embedding_integration.erl:155 — apps/agent_web/src/embedding_integration.erl:155-159 | apps/agent_web/src/embedding_integration.erl:290-294 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (5 lines × 2) apps/agent_web/src/endpoint_registry.erl:237 — apps/agent_web/src/endpoint_registry.erl:237-241 | apps/agent_web/src/endpoint_registry_ets.erl:174-178 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (5 lines × 2) apps/agent_web/src/mcp_oauth_client.erl:267 — apps/agent_web/src/mcp_oauth_client.erl:267-271 | apps/agent_web/src/mcp_oauth_client.erl:298-302 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (5 lines × 2) apps/agent_web/src/model_definition_manager.erl:213 — apps/agent_web/src/model_definition_manager.erl:213-217 | apps/agent_web/src/model_definition_manager.erl:352-356 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (5 lines × 2) apps/agent_web/src/model_definition_manager.erl:218 — apps/agent_web/src/model_definition_manager.erl:218-222 | apps/agent_web/src/model_definition_manager.erl:357-361 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (5 lines × 2) apps/agent_web/src/pipedream_auth_handler.erl:101 — apps/agent_web/src/pipedream_auth_handler.erl:101-106 | apps/agent_web/src/pipedream_auth_handler.erl:187-191 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (5 lines × 2) apps/agent_web/src/quantum_performance_analyzer.erl:365 — apps/agent_web/src/quantum_performance_analyzer.erl:365-369 | apps/agent_web/src/quantum_performance_analyzer.erl:562-566 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (5 lines × 2) apps/agent_web/src/training_data_generator.erl:151 — apps/agent_web/src/training_data_generator.erl:151-155 | apps/agents/src/agent_tools.erl:2981-2985 — 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) apps/agents/src/agent_instance.erl:1285 — apps/agents/src/agent_instance.erl:1285-1289 | apps/agents/src/agent_instance.erl:1478-1482 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (5 lines × 2) apps/agents/src/agent_instance.erl:1764 — apps/agents/src/agent_instance.erl:1764-1768 | apps/agents/src/agent_instance.erl:1773-1777 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (5 lines × 2) apps/agents/src/bulk_agent_creator.erl:224 — apps/agents/src/bulk_agent_creator.erl:224-228 | apps/agents/src/specialized_agent_templates.erl:1189-1193 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (5 lines × 2) apps/agents/src/subgoal_decomposition_engine.erl:264 — apps/agents/src/subgoal_decomposition_engine.erl:264-268 | apps/agents/src/subgoal_decomposition_engine.erl:310-314 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (5 lines × 2) apps/agent_web/src/agent_api_handler.erl:420 — apps/agent_web/src/agent_api_handler.erl:420-424 | apps/agent_web/src/agent_initializer.erl:18-22 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (5 lines × 2) apps/agent_web/src/crash_report_api_handler.erl:348 — apps/agent_web/src/crash_report_api_handler.erl:348-352 | apps/agent_web/src/error_interpretation_api_handler.erl:123-127 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (5 lines × 2) apps/agents/src/agent_protocol.erl:76 — apps/agents/src/agent_protocol.erl:76-80 | sandbox/myapp/apps/myapp/src/agent_protocol.erl:83-87 — before extracting anything, compare `apps/agents/src/agent_protocol.erl` and `sandbox/myapp/apps/myapp/src/agent_protocol.erl` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 2) apps/agents/src/agent_protocol.erl:96 — apps/agents/src/agent_protocol.erl:96-100 | sandbox/myapp/apps/myapp/src/agent_protocol.erl:103-107 — before extracting anything, compare `apps/agents/src/agent_protocol.erl` and `sandbox/myapp/apps/myapp/src/agent_protocol.erl` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 2) apps/agent_web/src/mcp_streamable_http_handler.erl:590 — apps/agent_web/src/mcp_streamable_http_handler.erl:590-594 | apps/agent_web/src/mcp_transport_streamable_http.erl:575-579 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (5 lines × 2) apps/agents/src/agent_communication_api.erl:190 — apps/agents/src/agent_communication_api.erl:190-195 | apps/agents/src/agent_tool_registry.erl:417-421 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (5 lines × 2) apps/agent_web/src/consciousness_bridge_api_handler.erl:94 — apps/agent_web/src/consciousness_bridge_api_handler.erl:94-98 | apps/agent_web/src/neural_swarm_api_handler.erl:80-84 — before extracting anything, compare `apps/agent_web/src/consciousness_bridge_api_handler.erl` and `apps/agent_web/src/neural_swarm_api_handler.erl` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 2) apps/agent_web/src/model_api_handler.erl:35 — apps/agent_web/src/model_api_handler.erl:35-39 | apps/agent_web/src/model_api_handler.erl:40-44 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (5 lines × 2) apps/openapi_scaffold/src/openapi_introspection_handler.erl:56 — apps/openapi_scaffold/src/openapi_introspection_handler.erl:56-60 | apps/openapi_scaffold/src/openapi_introspection_handler.erl:66-70 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (5 lines × 2) apps/agents/src/jina_tools.erl:461 — apps/agents/src/jina_tools.erl:461-465 | apps/agents/src/jina_tools.erl:499-503 — 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.
  • + 10 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×24
  • Duplicated block (6 lines × 2) apps/agent_web/src/claude_config_handler.erl:23 — apps/agent_web/src/claude_config_handler.erl:23-28 | apps/agent_web/src/oauth_handler.erl:169-174 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (6 lines × 2) apps/agent_web/src/consciousness_bridge_api_handler.erl:80 — apps/agent_web/src/consciousness_bridge_api_handler.erl:80-85 | apps/agent_web/src/neural_swarm_api_handler.erl:66-71 — before extracting anything, compare `apps/agent_web/src/consciousness_bridge_api_handler.erl` and `apps/agent_web/src/neural_swarm_api_handler.erl` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (6 lines × 2) apps/agent_web/src/hot_code_reloader.erl:176 — apps/agent_web/src/hot_code_reloader.erl:176-181 | apps/agent_web/src/hot_code_reloader.erl:195-200 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (6 lines × 2) apps/agent_web/src/mcp_advanced_config.erl:58 — apps/agent_web/src/mcp_advanced_config.erl:58-63 | apps/agent_web/src/mcp_advanced_config.erl:86-91 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (6 lines × 2) apps/agent_web/src/mcp_api_handler.erl:52 — apps/agent_web/src/mcp_api_handler.erl:52-57 | apps/agent_web/src/mcp_api_handler.erl:131-136 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (6 lines × 2) apps/agent_web/src/mcp_api_handler.erl:218 — apps/agent_web/src/mcp_api_handler.erl:218-223 | apps/agent_web/src/mcp_api_handler.erl:232-237 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (6 lines × 2) apps/agent_web/src/pipedream_mcp_client.erl:228 — apps/agent_web/src/pipedream_mcp_client.erl:228-233 | apps/agent_web/src/pipedream_mcp_client.erl:266-271 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (6 lines × 2) apps/agents/src/agent.erl:641 — apps/agents/src/agent.erl:641-646 | sandbox/myapp/apps/myapp/src/agent.erl:224-229 — before extracting anything, compare `apps/agents/src/agent.erl` and `sandbox/myapp/apps/myapp/src/agent.erl` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 154 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (6 lines × 2) apps/agents/src/agent_collaboration.erl:218 — apps/agents/src/agent_collaboration.erl:218-223 | apps/agents/src/agent_collaboration.erl:239-244 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (6 lines × 2) apps/agents/src/agent_registry.erl:78 — apps/agents/src/agent_registry.erl:78-83 | sandbox/myapp/apps/myapp/src/agent_registry.erl:71-76 — before extracting anything, compare `apps/agents/src/agent_registry.erl` and `sandbox/myapp/apps/myapp/src/agent_registry.erl` as WHOLE FILES: this scan already matched 4 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.
  • Duplicated block (6 lines × 2) apps/agents/src/agent_tool_registry.erl:124 — apps/agents/src/agent_tool_registry.erl:124-129 | apps/agents/src/agent_tool_registry.erl:154-159 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (6 lines × 2) apps/agents/src/specialized_agent_factory.erl:664 — apps/agents/src/specialized_agent_factory.erl:664-669 | apps/agents/src/specialized_agent_templates.erl:856-861 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (6 lines × 2) apps/openai/src/anthropic_client_template.erl:118 — apps/openai/src/anthropic_client_template.erl:118-123 | apps/openai/src/openai_client_template.erl:114-119 — before extracting anything, compare `apps/openai/src/anthropic_client_template.erl` and `apps/openai/src/openai_client_template.erl` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (6 lines × 2) apps/openai/src/openai_files.erl:301 — apps/openai/src/openai_files.erl:301-306 | apps/openai/src/openai_files.erl:333-338 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (6 lines × 2) apps/agent_web/src/conversation_handler.erl:334 — apps/agent_web/src/conversation_handler.erl:334-339 | apps/agent_web/src/conversation_initializer.erl:101-106 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (6 lines × 2) apps/openapi_scaffold/src/openapi_dynamic_handler.erl:239 — apps/openapi_scaffold/src/openapi_dynamic_handler.erl:239-244 | apps/openapi_scaffold/src/openapi_introspection_handler.erl:74-79 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (6 lines × 2) apps/agent_web/src/ai_error_processor.erl:215 — apps/agent_web/src/ai_error_processor.erl:215-220 | apps/agents/src/super_agent.erl:546-551 — 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) apps/agents/src/distributed_consciousness_engine.erl:644 — apps/agents/src/distributed_consciousness_engine.erl:644-649 | apps/agents/src/emergent_swarm_intelligence.erl:1170-1175 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (6 lines × 2) apps/agents/src/agent_instance.erl:930 — apps/agents/src/agent_instance.erl:930-935 | apps/agents/src/agent_instance.erl:1009-1015 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (6 lines × 2) apps/openai/src/openai_chat.erl:107 — apps/openai/src/openai_chat.erl:107-112 | apps/openai/src/openai_responses.erl:139-144 — before extracting anything, compare `apps/openai/src/openai_chat.erl` and `apps/openai/src/openai_responses.erl` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (6 lines × 2) apps/agents/src/agent_instance.erl:647 — apps/agents/src/agent_instance.erl:647-652 | apps/agents/src/agent_instance.erl:731-736 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (6 lines × 2) apps/openapi_scaffold/src/openapi_advanced_codegen.erl:393 — apps/openapi_scaffold/src/openapi_advanced_codegen.erl:393-398 | apps/openapi_scaffold/src/openapi_advanced_codegen.erl:949-954 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (6 lines × 2) apps/agent_web/src/embedding_integration.erl:432 — apps/agent_web/src/embedding_integration.erl:432-437 | apps/agent_web/src/embedding_integration.erl:442-447 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (6 lines × 2) apps/agent_web/src/embedding_integration.erl:473 — apps/agent_web/src/embedding_integration.erl:473-478 | apps/agent_web/src/hyper_graph_storage.erl:562-567 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×22
  • Duplicated block (9 lines × 2) apps/agent_web/src/consciousness_bridge_api_handler.erl:234 — apps/agent_web/src/consciousness_bridge_api_handler.erl:234-242 | apps/agent_web/src/neural_swarm_api_handler.erl:215-223 — before extracting anything, compare `apps/agent_web/src/consciousness_bridge_api_handler.erl` and `apps/agent_web/src/neural_swarm_api_handler.erl` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (9 lines × 2) apps/agent_web/src/embedding_integration.erl:530 — apps/agent_web/src/embedding_integration.erl:530-538 | apps/agent_web/src/hyper_graph_storage.erl:685-693 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (9 lines × 2) apps/agent_web/src/endpoint_registry.erl:296 — apps/agent_web/src/endpoint_registry.erl:296-304 | apps/agent_web/src/endpoint_registry.erl:308-316 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (9 lines × 2) apps/agent_web/src/mcp_agent_integration.erl:68 — apps/agent_web/src/mcp_agent_integration.erl:68-76 | apps/agent_web/src/mcp_agent_integration.erl:82-90 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (9 lines × 2) apps/agent_web/src/mcp_streamable_http_handler.erl:245 — apps/agent_web/src/mcp_streamable_http_handler.erl:245-253 | apps/agent_web/src/mcp_transport_streamable_http.erl:369-377 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (9 lines × 2) apps/agent_web/src/model_api_handler.erl:240 — apps/agent_web/src/model_api_handler.erl:240-248 | apps/agent_web/src/model_api_handler.erl:311-319 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (9 lines × 2) apps/agent_web/src/pipedream_mcp_client.erl:146 — apps/agent_web/src/pipedream_mcp_client.erl:146-154 | apps/agent_web/src/pipedream_mcp_client.erl:185-193 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (9 lines × 2) apps/agents/src/agent_registry.erl:101 — apps/agents/src/agent_registry.erl:101-109 | sandbox/myapp/apps/myapp/src/agent_registry.erl:98-106 — before extracting anything, compare `apps/agents/src/agent_registry.erl` and `sandbox/myapp/apps/myapp/src/agent_registry.erl` as WHOLE FILES: this scan already matched 4 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.
  • Duplicated block (9 lines × 2) apps/agents/src/agent_tools.erl:1851 — apps/agents/src/agent_tools.erl:1851-1859 | apps/agents/src/agent_tools.erl:1891-1899 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (9 lines × 2) apps/agents/src/jina_tools.erl:18 — apps/agents/src/jina_tools.erl:18-26 | apps/agents/src/jina_tools.erl:54-62 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (9 lines × 2) apps/agents/src/streaming_function_handler.erl:561 — apps/agents/src/streaming_function_handler.erl:561-569 | apps/openai/src/json_serializer.erl:74-82 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (9 lines × 2) apps/openai/src/openai_chat.erl:360 — apps/openai/src/openai_chat.erl:360-368 | apps/openai/src/openai_responses.erl:547-555 — before extracting anything, compare `apps/openai/src/openai_chat.erl` and `apps/openai/src/openai_responses.erl` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (9 lines × 2) apps/openapi_scaffold/src/openapi_graphql_bridge.erl:235 — apps/openapi_scaffold/src/openapi_graphql_bridge.erl:235-243 | apps/openapi_scaffold/src/openapi_graphql_bridge.erl:463-471 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (9 lines × 2) apps/openapi_scaffold/src/openapi_graphql_bridge.erl:513 — apps/openapi_scaffold/src/openapi_graphql_bridge.erl:513-521 | apps/openapi_scaffold/src/openapi_graphql_bridge.erl:531-539 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (9 lines × 2) apps/agents/src/agent_discovery.erl:123 — apps/agents/src/agent_discovery.erl:123-131 | sandbox/myapp/apps/myapp/src/agent_discovery.erl:129-137 — before extracting anything, compare `apps/agents/src/agent_discovery.erl` and `sandbox/myapp/apps/myapp/src/agent_discovery.erl` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 382 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (9 lines × 2) apps/agent_web/src/conversation_handler.erl:346 — apps/agent_web/src/conversation_handler.erl:346-354 | apps/agent_web/src/timeline_handler.erl:284-292 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (9 lines × 2) apps/agent_web/src/super_agent_handler.erl:254 — apps/agent_web/src/super_agent_handler.erl:254-262 | apps/agent_web/src/super_agent_handler.erl:272-280 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (9 lines × 2) apps/agent_web/src/agent_scheduling_handler.erl:47 — apps/agent_web/src/agent_scheduling_handler.erl:47-55 | apps/agent_web/src/agent_scheduling_handler.erl:65-73 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (9 lines × 2) apps/agent_web/src/bulk_operations_handler.erl:30 — apps/agent_web/src/bulk_operations_handler.erl:30-38 | apps/agent_web/src/workflow_api_handler.erl:31-39 — before extracting anything, compare `apps/agent_web/src/bulk_operations_handler.erl` and `apps/agent_web/src/workflow_api_handler.erl` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (9 lines × 2) apps/agent_web/src/embedding_integration.erl:272 — apps/agent_web/src/embedding_integration.erl:272-280 | apps/agent_web/src/embedding_integration.erl:296-304 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (9 lines × 2) apps/agent_web/src/logs_api_handler.erl:73 — apps/agent_web/src/logs_api_handler.erl:73-81 | apps/agent_web/src/logs_api_handler.erl:101-109 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (9 lines × 2) apps/openai/src/token_stream_integration.erl:87 — apps/openai/src/token_stream_integration.erl:87-95 | apps/openai/src/token_stream_integration.erl:101-109 — 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.
P7 · Outbound HTTP resilience · Outbound HTTP without resilience · ×22
  • Outbound HTTP without resilience apps/agent_web/src/embedding_integration.erl:410 — `httpc:request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience apps/agent_web/src/mcp_oauth_client.erl:269 — `httpc:request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience apps/agent_web/src/mcp_oauth_client.erl:300 — `httpc:request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience apps/agent_web/src/mcp_oauth_client.erl:335 — `httpc:request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience apps/agent_web/src/mcp_oauth_integration.erl:217 — `httpc:request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience apps/agent_web/src/mcp_oauth_integration.erl:437 — `httpc:request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience apps/agent_web/src/oauth_handler.erl:272 — `httpc:request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience apps/agent_web/src/openapi_fetcher.erl:164 — `httpc:request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience apps/agent_web/src/pipedream_mcp_client.erl:130 — `httpc:request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience apps/agent_web/src/pipedream_mcp_client.erl:152 — `httpc:request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience apps/agent_web/src/pipedream_mcp_client.erl:191 — `httpc:request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience apps/agent_web/src/pipedream_mcp_client.erl:232 — `httpc:request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience apps/agent_web/src/pipedream_mcp_client.erl:270 — `httpc:request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience apps/agents/src/agent_tools.erl:1793 — `httpc:request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience apps/agents/src/agent_tools.erl:1797 — `httpc:request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience apps/agents/src/agent_tools.erl:1800 — `httpc:request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience apps/agents/src/enhanced_agent_tools.erl:364 — `httpc:request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience apps/openapi_scaffold/src/openapi_graphql_bridge.erl:641 — `hackney: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.
  • Outbound HTTP without resilience apps/openapi_scaffold/src/openapi_graphql_bridge.erl:665 — `hackney:request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience apps/openapi_scaffold/src/openapi_graphql_bridge.erl:788 — `gun:open(` 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 apps/openapi_scaffold/src/openapi_playground.erl:583 — `hackney:request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience apps/openapi_scaffold/src/openapi_time_travel.erl:352 — `hackney:request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×21
  • Duplicated block (7 lines × 2) apps/agent_web/src/agent_scheduling_handler.erl:49 — apps/agent_web/src/agent_scheduling_handler.erl:49-55 | apps/agent_web/src/agent_scheduling_handler.erl:259-265 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (7 lines × 2) apps/agent_web/src/ai_error_interpreter.erl:139 — apps/agent_web/src/ai_error_interpreter.erl:139-145 | apps/agent_web/src/crash_report_processor.erl:171-177 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (7 lines × 2) apps/agent_web/src/bulk_operations_handler.erl:226 — apps/agent_web/src/bulk_operations_handler.erl:226-234 | apps/agent_web/src/bulk_operations_handler.erl:278-284 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (7 lines × 2) apps/agent_web/src/crash_report_api_handler.erl:188 — apps/agent_web/src/crash_report_api_handler.erl:188-194 | apps/agent_web/src/crash_report_ws_handler.erl:162-168 — before extracting anything, compare `apps/agent_web/src/crash_report_api_handler.erl` and `apps/agent_web/src/crash_report_ws_handler.erl` as WHOLE FILES: this scan already matched 5 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (7 lines × 2) apps/agent_web/src/mcp_cli.erl:260 — apps/agent_web/src/mcp_cli.erl:260-266 | apps/agent_web/src/mcp_cli.erl:273-279 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (7 lines × 2) apps/agent_web/src/mcp_cli.erl:316 — apps/agent_web/src/mcp_cli.erl:316-322 | apps/agent_web/src/mcp_cli.erl:329-335 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (7 lines × 2) apps/agent_web/src/super_agent_handler.erl:66 — apps/agent_web/src/super_agent_handler.erl:66-72 | apps/agent_web/src/super_agent_handler.erl:93-99 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (7 lines × 2) apps/agents/src/agent_tools.erl:1343 — apps/agents/src/agent_tools.erl:1343-1349 | sandbox/myapp/apps/myapp/src/agent_tools.erl:284-290 — before extracting anything, compare `apps/agents/src/agent_tools.erl` and `sandbox/myapp/apps/myapp/src/agent_tools.erl` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 223 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (7 lines × 2) apps/openai/src/openai_chat.erl:352 — apps/openai/src/openai_chat.erl:352-358 | apps/openai/src/openai_responses.erl:277-283 — before extracting anything, compare `apps/openai/src/openai_chat.erl` and `apps/openai/src/openai_responses.erl` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (7 lines × 2) apps/openai/src/openai_chat.erl:398 — apps/openai/src/openai_chat.erl:398-404 | apps/openai/src/openai_responses.erl:589-595 — before extracting anything, compare `apps/openai/src/openai_chat.erl` and `apps/openai/src/openai_responses.erl` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (7 lines × 2) apps/openai/src/openai_files.erl:190 — apps/openai/src/openai_files.erl:190-196 | apps/openai/src/openai_responses.erl:181-187 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (7 lines × 2) apps/openapi_scaffold/src/openapi_proxy.erl:246 — apps/openapi_scaffold/src/openapi_proxy.erl:246-252 | apps/openapi_scaffold/src/openapi_validator.erl:446-452 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (7 lines × 2) apps/agents/src/agent_discovery.erl:339 — apps/agents/src/agent_discovery.erl:339-345 | sandbox/myapp/apps/myapp/src/agent_discovery.erl:355-361 — before extracting anything, compare `apps/agents/src/agent_discovery.erl` and `sandbox/myapp/apps/myapp/src/agent_discovery.erl` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 382 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (7 lines × 2) apps/agent_web/src/agent_execute_handler.erl:44 — apps/agent_web/src/agent_execute_handler.erl:44-50 | apps/agent_web/src/agent_execute_handler.erl:57-63 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (7 lines × 2) apps/agent_web/src/bulk_operations_handler.erl:60 — apps/agent_web/src/bulk_operations_handler.erl:60-66 | apps/agent_web/src/workflow_api_handler.erl:61-67 — before extracting anything, compare `apps/agent_web/src/bulk_operations_handler.erl` and `apps/agent_web/src/workflow_api_handler.erl` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (7 lines × 2) apps/openapi_scaffold/src/openapi_validator.erl:124 — apps/openapi_scaffold/src/openapi_validator.erl:124-130 | apps/openapi_scaffold/src/openapi_validator.erl:171-177 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (7 lines × 2) apps/agent_web/src/agent_execute_handler.erl:31 — apps/agent_web/src/agent_execute_handler.erl:31-37 | apps/agent_web/src/knowledge_base_handler.erl:104-110 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (7 lines × 2) apps/agent_web/src/mcp_management_handler.erl:226 — apps/agent_web/src/mcp_management_handler.erl:226-232 | apps/agent_web/src/mcp_management_handler.erl:300-306 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (7 lines × 2) apps/agent_web/src/fleet_management_handler.erl:14 — apps/agent_web/src/fleet_management_handler.erl:14-20 | apps/agent_web/src/fleet_management_handler.erl:79-85 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (7 lines × 2) apps/agent_web/src/model_api_handler.erl:95 — apps/agent_web/src/model_api_handler.erl:95-101 | apps/agent_web/src/model_api_handler.erl:127-133 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (7 lines × 2) apps/agent_web/src/mcp_transport_streamable_http.erl:169 — apps/agent_web/src/mcp_transport_streamable_http.erl:169-175 | apps/agent_web/src/mcp_transport_streamable_http.erl:188-194 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×20
  • Duplicated block (8 lines × 2) apps/agent_web/src/colored_logger_handler.erl:156 — apps/agent_web/src/colored_logger_handler.erl:156-163 | apps/agent_web/src/simple_logger.erl:56-63 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (8 lines × 2) apps/agent_web/src/consciousness_bridge_api_handler.erl:38 — apps/agent_web/src/consciousness_bridge_api_handler.erl:38-45 | apps/agent_web/src/neural_swarm_api_handler.erl:38-45 — before extracting anything, compare `apps/agent_web/src/consciousness_bridge_api_handler.erl` and `apps/agent_web/src/neural_swarm_api_handler.erl` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (8 lines × 2) apps/agent_web/src/conversation_handler.erl:144 — apps/agent_web/src/conversation_handler.erl:144-151 | apps/agent_web/src/conversation_handler.erl:204-211 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (8 lines × 2) apps/agent_web/src/mcp_cli.erl:287 — apps/agent_web/src/mcp_cli.erl:287-294 | apps/agent_web/src/mcp_cli.erl:300-307 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (8 lines × 2) apps/agent_web/src/mcp_oauth_handler.erl:73 — apps/agent_web/src/mcp_oauth_handler.erl:73-80 | apps/agent_web/src/mcp_oauth_handler.erl:148-155 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (8 lines × 2) apps/agent_web/src/ssl_cert_handler.erl:25 — apps/agent_web/src/ssl_cert_handler.erl:25-32 | apps/agent_web/src/system_health_handler.erl:15-22 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (8 lines × 2) apps/agents/src/agent_discovery.erl:353 — apps/agents/src/agent_discovery.erl:353-360 | sandbox/myapp/apps/myapp/src/agent_discovery.erl:369-376 — before extracting anything, compare `apps/agents/src/agent_discovery.erl` and `sandbox/myapp/apps/myapp/src/agent_discovery.erl` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 382 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (8 lines × 2) apps/agents/src/agent_tools.erl:1976 — apps/agents/src/agent_tools.erl:1976-1983 | apps/agents/src/jina_tools.erl:131-138 — before extracting anything, compare `apps/agents/src/agent_tools.erl` and `apps/agents/src/jina_tools.erl` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 201 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (8 lines × 2) apps/agents/src/agent_tools.erl:1997 — apps/agents/src/agent_tools.erl:1997-2004 | apps/agents/src/jina_tools.erl:257-264 — before extracting anything, compare `apps/agents/src/agent_tools.erl` and `apps/agents/src/jina_tools.erl` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 201 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (8 lines × 2) apps/agents/src/agent_tools.erl:2022 — apps/agents/src/agent_tools.erl:2022-2029 | apps/agents/src/jina_tools.erl:151-158 — before extracting anything, compare `apps/agents/src/agent_tools.erl` and `apps/agents/src/jina_tools.erl` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 201 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (8 lines × 2) apps/agents/src/agent_protocol.erl:49 — apps/agents/src/agent_protocol.erl:49-56 | sandbox/myapp/apps/myapp/src/agent_protocol.erl:56-63 — before extracting anything, compare `apps/agents/src/agent_protocol.erl` and `sandbox/myapp/apps/myapp/src/agent_protocol.erl` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (8 lines × 2) apps/agents/src/agent_protocol.erl:203 — apps/agents/src/agent_protocol.erl:203-210 | sandbox/myapp/apps/myapp/src/agent_protocol.erl:210-217 — before extracting anything, compare `apps/agents/src/agent_protocol.erl` and `sandbox/myapp/apps/myapp/src/agent_protocol.erl` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (8 lines × 2) apps/openapi_scaffold/src/openapi_scaffold_sup.erl:10 — apps/openapi_scaffold/src/openapi_scaffold_sup.erl:10-17 | sandbox/myapp/apps/myapp/src/agent.erl:116-127 — 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) apps/agent_web/src/pagination_utils.erl:159 — apps/agent_web/src/pagination_utils.erl:159-166 | apps/agents/src/agent_quorum.erl:276-283 — 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) apps/agent_web/src/consciousness_bridge_api_handler.erl:132 — apps/agent_web/src/consciousness_bridge_api_handler.erl:132-139 | apps/agent_web/src/neural_swarm_api_handler.erl:120-127 — before extracting anything, compare `apps/agent_web/src/consciousness_bridge_api_handler.erl` and `apps/agent_web/src/neural_swarm_api_handler.erl` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (8 lines × 2) apps/agent_web/src/model_api_handler.erl:327 — apps/agent_web/src/model_api_handler.erl:327-334 | apps/agent_web/src/model_api_handler.erl:521-528 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (8 lines × 2) apps/agent_web/src/model_definition_manager.erl:92 — apps/agent_web/src/model_definition_manager.erl:92-99 | apps/agent_web/src/model_definition_manager.erl:120-127 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (8 lines × 2) apps/agent_web/src/mcp_client_v2.erl:392 — apps/agent_web/src/mcp_client_v2.erl:392-399 | apps/agent_web/src/mcp_transport.erl:154-161 — before extracting anything, compare `apps/agent_web/src/mcp_client_v2.erl` and `apps/agent_web/src/mcp_transport.erl` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (8 lines × 2) apps/agent_web/src/mcp_server_handler.erl:149 — apps/agent_web/src/mcp_server_handler.erl:149-156 | apps/agent_web/src/mcp_server_handler.erl:227-234 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (8 lines × 2) apps/agent_web/src/ssl_cert_handler.erl:108 — apps/agent_web/src/ssl_cert_handler.erl:108-115 | apps/agent_web/src/ssl_cert_handler.erl:135-142 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×17
  • Duplicated block (11 lines × 2) apps/agent_web/src/agent_api_handler.erl:197 — apps/agent_web/src/agent_api_handler.erl:197-207 | apps/agent_web/src/agent_api_handler.erl:276-286 — 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 (11 lines × 2) apps/agent_web/src/agent_communication_handler.erl:54 — apps/agent_web/src/agent_communication_handler.erl:54-64 | apps/agent_web/src/agent_quorum_handler.erl:51-61 — before extracting anything, compare `apps/agent_web/src/agent_communication_handler.erl` and `apps/agent_web/src/agent_quorum_handler.erl` as WHOLE FILES: this scan already matched 4 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (11 lines × 2) apps/agent_web/src/agent_execute_handler.erl:32 — apps/agent_web/src/agent_execute_handler.erl:32-42 | apps/agent_web/src/agent_templates_handler.erl:28-38 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (11 lines × 2) apps/agent_web/src/agent_scheduling_handler.erl:343 — apps/agent_web/src/agent_scheduling_handler.erl:343-353 | apps/agent_web/src/timeline_ws_handler.erl:339-351 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (11 lines × 2) apps/agent_web/src/distributed_consensus_tracker.erl:447 — apps/agent_web/src/distributed_consensus_tracker.erl:447-457 | apps/agent_web/src/distributed_consensus_tracker.erl:720-730 — 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 (11 lines × 2) apps/agent_web/src/mcp_api_handler.erl:31 — apps/agent_web/src/mcp_api_handler.erl:31-41 | apps/agent_web/src/mcp_api_handler.erl:113-123 — 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 (11 lines × 2) apps/agent_web/src/pdf_processing_integration.erl:347 — apps/agent_web/src/pdf_processing_integration.erl:347-357 | apps/agent_web/src/pdf_processing_integration.erl:363-373 — 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 (11 lines × 2) apps/agent_web/src/pipedream_mcp_client.erl:236 — apps/agent_web/src/pipedream_mcp_client.erl:236-246 | apps/agent_web/src/pipedream_mcp_client.erl:274-284 — 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 (11 lines × 2) apps/agent_web/src/ssl_cert_handler.erl:34 — apps/agent_web/src/ssl_cert_handler.erl:34-44 | apps/agent_web/src/system_health_handler.erl:32-42 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (11 lines × 2) apps/agent_web/src/workflow_api_handler.erl:128 — apps/agent_web/src/workflow_api_handler.erl:128-138 | apps/agent_web/src/workflow_api_handler.erl:174-184 — 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 (11 lines × 2) apps/agents/src/agent_registry.erl:126 — apps/agents/src/agent_registry.erl:126-136 | sandbox/myapp/apps/myapp/src/agent_registry.erl:123-133 — before extracting anything, compare `apps/agents/src/agent_registry.erl` and `sandbox/myapp/apps/myapp/src/agent_registry.erl` as WHOLE FILES: this scan already matched 4 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.
  • Duplicated block (11 lines × 2) apps/agents/src/agent_uuid.erl:13 — apps/agents/src/agent_uuid.erl:13-23 | sandbox/myapp/apps/myapp/src/uuid.erl:12-22 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (11 lines × 2) apps/agents/src/agent_discovery.erl:458 — apps/agents/src/agent_discovery.erl:458-468 | sandbox/myapp/apps/myapp/src/agent_discovery.erl:474-484 — before extracting anything, compare `apps/agents/src/agent_discovery.erl` and `sandbox/myapp/apps/myapp/src/agent_discovery.erl` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 382 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (11 lines × 2) apps/agent_web/src/crash_report_api_handler.erl:220 — apps/agent_web/src/crash_report_api_handler.erl:220-230 | apps/agent_web/src/crash_report_ws_handler.erl:194-204 — before extracting anything, compare `apps/agent_web/src/crash_report_api_handler.erl` and `apps/agent_web/src/crash_report_ws_handler.erl` as WHOLE FILES: this scan already matched 5 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (11 lines × 2) apps/openai/src/anthropic_client_template.erl:16 — apps/openai/src/anthropic_client_template.erl:16-26 | apps/openai/src/openai_client_template.erl:14-24 — before extracting anything, compare `apps/openai/src/anthropic_client_template.erl` and `apps/openai/src/openai_client_template.erl` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (11 lines × 2) apps/agent_web/src/mcp_management_handler.erl:335 — apps/agent_web/src/mcp_management_handler.erl:335-345 | apps/agent_web/src/mcp_management_handler.erl:351-361 — 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 (11 lines × 2) apps/openapi_scaffold/src/openapi_validator.erl:149 — apps/openapi_scaffold/src/openapi_validator.erl:149-159 | apps/openapi_scaffold/src/openapi_validator.erl:196-206 — 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.
AC6 · Visual & motion safety · Animation without a prefers-reduced-motion guard · ×16
  • Animation without a prefers-reduced-motion guard apps/agent_web/frontend/src/components/AdvancedStructuredOutputsManager.tsx:421 — <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
  • Animation without a prefers-reduced-motion guard apps/agent_web/frontend/src/components/ClaudeCLI.tsx:250 — <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
  • Animation without a prefers-reduced-motion guard apps/agent_web/frontend/src/components/MCPOrchestrationEngine.tsx:454 — <div> moves — its `animate-ping` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
  • Animation without a prefers-reduced-motion guard REDACTED:1102 — <div> moves — its `animate-bounce` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
  • Animation without a prefers-reduced-motion guard REDACTED:1103 — <div> moves — its `animate-bounce` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
  • Animation without a prefers-reduced-motion guard REDACTED:1104 — <div> moves — its `animate-bounce` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
  • Animation without a prefers-reduced-motion guard REDACTED:1251 — <div> moves — its inline style sets `animation: fadeInUp 0.3s ease-out` — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
  • Animation without a prefers-reduced-motion guard apps/agent_web/priv/static/css/style.css:86 — `.header::before` moves (`animation: shimmer 20s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard apps/agent_web/priv/static/css/style.css:172 — `.agent-item::before` moves (`transition: transform 0.6s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard apps/agent_web/priv/static/css/style.css:283 — `.btn::before` moves (`transition: width 0.6s, height 0.6s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard apps/agent_web/priv/static/css/style.css:350 — `.example-card::before` moves (`transition: transform 0.3s cubic-bezier(0.4, 0, 0.2, 1)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard apps/agent_web/priv/static/css/style.css:390 — `.message` moves (`animation: fadeInUp 0.3s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard apps/agent_web/priv/static/css/style.css:463 — `.status-indicator::before` moves (`animation: pulse 2s cubic-bezier(0.4, 0, 0.6, 1) infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard apps/agent_web/priv/static/css/style.css:767 — `.status-indicator.pulsing` moves (`animation: pulse 2s infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard apps/agent_web/priv/static/css/style.css:820 — `.connection.active` moves (`animation: flow 2s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard apps/agent_web/priv/static/css/style.css:1054 — `.notification` moves (`animation: slideIn 0.3s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
D17 · Explicit Debt · TodoComment · ×14
  • TodoComment apps/openapi_scaffold/src/openapi_parser.erl:222 — %% TODO: Implement $ref resolution — 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 apps/openapi_scaffold/src/openapi_validator.erl:440 — %% TODO: Implement response validation — 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 apps/openai/src/openai_self_scaffold.erl:531 — %% TODO: Implement type validation based on spec — 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 apps/agents/src/agent_instance.erl:1269 — % TODO: Implement proper multi-turn function calling for Responses API — 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 apps/agents/src/dynamic_agent_router.erl:390 — % TODO: Implement path affinity logic — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `% REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment apps/agents/src/dynamic_agent_router.erl:398 — % TODO: Implement conversation history affinity — 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 apps/agents/src/mcp_server_config.erl:679 — %% TODO: Implement actual MCP capability discovery — 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 apps/agent_web/src/crash_report_api_handler.erl:341 — %% TODO: Implement automated fix application — 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 apps/agent_web/src/crash_report_api_handler.erl:345 — %% TODO: Implement crash report deletion — 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 apps/agent_web/src/crash_report_ws_handler.erl:101 — %% TODO: Implement filtered subscriptions — 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 apps/agent_web/src/oauth_handler.erl:419 — % TODO: Implement refresh token logic — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `% REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment apps/agent_web/src/timeline_ws_handler.erl:278 — %% TODO: Implement unsubscribe from timeline_event_store — 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 apps/agent_web/src/timeline_ws_handler.erl:359 — %% TODO: Implement cleanup for timeline_event_store — 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 apps/agent_web/frontend/src/components/MonitoringPanel.tsx:119 — // TODO: Implement agent details view — 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.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×14
  • Duplicated block (12 lines × 2) apps/agent_web/src/agent_communication_handler.erl:29 — apps/agent_web/src/agent_communication_handler.erl:29-40 | apps/agent_web/src/agent_quorum_handler.erl:26-37 — before extracting anything, compare `apps/agent_web/src/agent_communication_handler.erl` and `apps/agent_web/src/agent_quorum_handler.erl` as WHOLE FILES: this scan already matched 4 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (12 lines × 2) apps/agent_web/src/agent_scheduling_handler.erl:133 — apps/agent_web/src/agent_scheduling_handler.erl:133-144 | apps/agent_web/src/agent_scheduling_handler.erl:233-244 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (12 lines × 2) apps/agent_web/src/colored_logger.erl:308 — apps/agent_web/src/colored_logger.erl:308-319 | apps/agent_web/src/colored_logger.erl:346-357 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (12 lines × 2) apps/agent_web/src/endpoint_registry.erl:118 — apps/agent_web/src/endpoint_registry.erl:118-129 | apps/agent_web/src/endpoint_registry.erl:148-159 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (12 lines × 2) apps/agent_web/src/mcp_cli.erl:341 — apps/agent_web/src/mcp_cli.erl:341-352 | apps/agent_web/src/mcp_cli.erl:362-373 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (12 lines × 2) apps/agents/src/agent_quorum.erl:97 — apps/agents/src/agent_quorum.erl:97-108 | apps/agents/src/agent_quorum.erl:173-184 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (12 lines × 2) apps/agents/src/agent_tools.erl:259 — apps/agents/src/agent_tools.erl:259-270 | apps/agents/src/agent_tools.erl:292-303 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (12 lines × 2) apps/agents/src/agent_tools.erl:330 — apps/agents/src/agent_tools.erl:330-341 | sandbox/myapp/apps/myapp/src/agent_tools.erl:174-185 — before extracting anything, compare `apps/agents/src/agent_tools.erl` and `sandbox/myapp/apps/myapp/src/agent_tools.erl` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 223 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (12 lines × 2) apps/agents/src/agent_tools.erl:1804 — apps/agents/src/agent_tools.erl:1804-1815 | sandbox/myapp/apps/myapp/src/agent_tools.erl:383-394 — before extracting anything, compare `apps/agents/src/agent_tools.erl` and `sandbox/myapp/apps/myapp/src/agent_tools.erl` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 223 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (12 lines × 2) apps/agents/src/jina_tools.erl:480 — apps/agents/src/jina_tools.erl:480-491 | apps/agents/src/jina_tools.erl:518-529 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (12 lines × 2) apps/openai/src/anthropic_client_template.erl:29 — apps/openai/src/anthropic_client_template.erl:29-40 | apps/openai/src/openai_client_template.erl:27-38 — before extracting anything, compare `apps/openai/src/anthropic_client_template.erl` and `apps/openai/src/openai_client_template.erl` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (12 lines × 2) apps/openai/src/openai_streaming.erl:90 — apps/openai/src/openai_streaming.erl:90-101 | apps/openai/src/openai_streaming.erl:107-118 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (12 lines × 2) apps/openapi_scaffold/src/openapi_router.erl:51 — apps/openapi_scaffold/src/openapi_router.erl:51-62 | apps/openapi_scaffold/src/openapi_router.erl:67-78 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (12 lines × 2) apps/openai/src/token_stream_integration.erl:65 — apps/openai/src/token_stream_integration.erl:65-76 | apps/openai/src/token_stream_integration.erl:130-141 — 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.
D3 · God Classes · ClassTooLong · ×13
  • ClassTooLong: AdvancedMCPDashboard REDACTED:1 — ClassTooLong — 832 significant lines (blank, comment-only and punctuation-only lines excluded), 7 methods. The bar is 400 significant lines; this is 432 over it, 2.08× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: ModelTypeEditor apps/agent_web/frontend/src/components/ModelTypeEditor.tsx:1 — ClassTooLong — 678 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 278 over it, 1.70× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: SimpleAdvancedChat REDACTED:1 — ClassTooLong — 628 significant lines (blank, comment-only and punctuation-only lines excluded), 6 methods. The bar is 400 significant lines; this is 228 over it, 1.57× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: ComprehensiveMCPManager apps/agent_web/frontend/src/components/ComprehensiveMCPManager.tsx:1 — ClassTooLong — 539 significant lines (blank, comment-only and punctuation-only lines excluded), 6 methods. The bar is 400 significant lines; this is 139 over it, 1.35× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: App apps/agent_web/frontend/src/App.tsx:1 — ClassTooLong — 528 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 128 over it, 1.32× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: CrashMonitorDashboard apps/agent_web/frontend/src/components/CrashMonitorDashboard.tsx:1 — ClassTooLong — 491 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 91 over it, 1.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: DiscoveryMeshDashboard apps/agent_web/frontend/src/components/DiscoveryMeshDashboard.tsx:1 — ClassTooLong — 476 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 76 over it, 1.19× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: UltimatePerformanceDashboard apps/agent_web/frontend/src/components/UltimatePerformanceDashboard.tsx:1 — ClassTooLong — 472 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 72 over it, 1.18× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: ModelConfiguration apps/agent_web/frontend/src/components/ModelConfiguration.tsx:1 — ClassTooLong — 459 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 59 over it, 1.15× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: AdvancedStructuredOutputsManager apps/agent_web/frontend/src/components/AdvancedStructuredOutputsManager.tsx:1 — ClassTooLong — 448 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 48 over it, 1.12× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: QuantumConsciousnessInterface apps/agent_web/frontend/src/components/QuantumConsciousnessInterface.tsx:1 — ClassTooLong — 448 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 48 over it, 1.12× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: AdaptiveAIInterface apps/agent_web/frontend/src/components/AdaptiveAIInterface.tsx:1 — ClassTooLong — 429 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 29 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: Timeline apps/agent_web/frontend/src/components/Timeline.tsx:1 — ClassTooLong — 401 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 1 over it, 1.00× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
AC2 · Forms & labels · <Select> field component without a label · ×11
  • <Select> field component without a label apps/agent_web/frontend/src/components/AdvancedStructuredOutputsManager.tsx:351 — This select is named only by the placeholder of its value part. Nothing is typed into a select, so the placeholder does not vanish on input: it is shown as the trigger's text until a value is chosen, and then the chosen value replaces it — so at no point does the control state what the choice is for, and the trigger's role (combobox) takes its name from the author, not from that text. Name it: an aria-label on the trigger, or an id on the trigger with a <label htmlFor> pointing at it.
  • <Select> field component without a label apps/agent_web/frontend/src/components/AgentCommunicationPanel.tsx:150 — This select is named only by the placeholder of its value part. Nothing is typed into a select, so the placeholder does not vanish on input: it is shown as the trigger's text until a value is chosen, and then the chosen value replaces it — so at no point does the control state what the choice is for, and the trigger's role (combobox) takes its name from the author, not from that text. Name it: an aria-label on the trigger, or an id on the trigger with a <label htmlFor> pointing at it.
  • <Select> field component without a label apps/agent_web/frontend/src/components/AgentCommunicationPanel.tsx:164 — This select is named only by the placeholder of its value part. Nothing is typed into a select, so the placeholder does not vanish on input: it is shown as the trigger's text until a value is chosen, and then the chosen value replaces it — so at no point does the control state what the choice is for, and the trigger's role (combobox) takes its name from the author, not from that text. Name it: an aria-label on the trigger, or an id on the trigger with a <label htmlFor> pointing at it.
  • <Select> field component without a label apps/agent_web/frontend/src/components/AgentCommunicationPanel.tsx:179 — This select is named only by the placeholder of its value part. Nothing is typed into a select, so the placeholder does not vanish on input: it is shown as the trigger's text until a value is chosen, and then the chosen value replaces it — so at no point does the control state what the choice is for, and the trigger's role (combobox) takes its name from the author, not from that text. Name it: an aria-label on the trigger, or an id on the trigger with a <label htmlFor> pointing at it.
  • <Select> field component without a label apps/agent_web/frontend/src/components/AgentCommunicationPanel.tsx:255 — This select is named only by the placeholder of its value part. Nothing is typed into a select, so the placeholder does not vanish on input: it is shown as the trigger's text until a value is chosen, and then the chosen value replaces it — so at no point does the control state what the choice is for, and the trigger's role (combobox) takes its name from the author, not from that text. Name it: an aria-label on the trigger, or an id on the trigger with a <label htmlFor> pointing at it.
  • <Select> field component without a label apps/agent_web/frontend/src/components/AgentCommunicationPanel.tsx:268 — This select is named only by the placeholder of its value part. Nothing is typed into a select, so the placeholder does not vanish on input: it is shown as the trigger's text until a value is chosen, and then the chosen value replaces it — so at no point does the control state what the choice is for, and the trigger's role (combobox) takes its name from the author, not from that text. Name it: an aria-label on the trigger, or an id on the trigger with a <label htmlFor> pointing at it.
  • <Select> field component without a label apps/agent_web/frontend/src/components/CrashMonitorDashboard.tsx:380 — This select is named only by the placeholder of its value part. Nothing is typed into a select, so the placeholder does not vanish on input: it is shown as the trigger's text until a value is chosen, and then the chosen value replaces it — so at no point does the control state what the choice is for, and the trigger's role (combobox) takes its name from the author, not from that text. Name it: an aria-label on the trigger, or an id on the trigger with a <label htmlFor> pointing at it.
  • <Select> field component without a label apps/agent_web/frontend/src/components/CrashMonitorDashboard.tsx:392 — This select is named only by the placeholder of its value part. Nothing is typed into a select, so the placeholder does not vanish on input: it is shown as the trigger's text until a value is chosen, and then the chosen value replaces it — so at no point does the control state what the choice is for, and the trigger's role (combobox) takes its name from the author, not from that text. Name it: an aria-label on the trigger, or an id on the trigger with a <label htmlFor> pointing at it.
  • <Select> field component without a label apps/agent_web/frontend/src/components/CreateAgentDialog.tsx:64 — This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id alone, wherever it is set, names nothing until a label points at it). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <Select> field component without a label apps/agent_web/frontend/src/components/DiscoveryMeshDashboard.tsx:408 — This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id alone, wherever it is set, names nothing until a label points at it). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <Select> field component without a label apps/agent_web/frontend/src/components/FleetManagementDashboard.tsx:346 — This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id alone, wherever it is set, names nothing until a label points at it). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×11
  • Duplicated block (10 lines × 2) apps/agent_web/src/mcp_management_handler.erl:60 — apps/agent_web/src/mcp_management_handler.erl:60-69 | apps/agent_web/src/mcp_management_handler.erl:95-104 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (10 lines × 2) apps/agent_web/src/mcp_streamable_http_handler.erl:142 — apps/agent_web/src/mcp_streamable_http_handler.erl:142-151 | apps/agent_web/src/mcp_streamable_http_handler.erl:240-249 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (10 lines × 2) apps/agent_web/src/super_agent_handler.erl:56 — apps/agent_web/src/super_agent_handler.erl:56-65 | apps/agent_web/src/super_agent_handler.erl:89-98 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (10 lines × 2) apps/agent_web/src/training_data_generator.erl:156 — apps/agent_web/src/training_data_generator.erl:156-165 | apps/agents/src/agent_tools.erl:2986-2995 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (10 lines × 2) apps/agents/src/agent_registry.erl:115 — apps/agents/src/agent_registry.erl:115-124 | sandbox/myapp/apps/myapp/src/agent_registry.erl:112-121 — before extracting anything, compare `apps/agents/src/agent_registry.erl` and `sandbox/myapp/apps/myapp/src/agent_registry.erl` as WHOLE FILES: this scan already matched 4 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.
  • Duplicated block (10 lines × 2) apps/agents/src/agent_tools.erl:971 — apps/agents/src/agent_tools.erl:971-980 | sandbox/myapp/apps/myapp/src/agent_tools.erl:218-227 — before extracting anything, compare `apps/agents/src/agent_tools.erl` and `sandbox/myapp/apps/myapp/src/agent_tools.erl` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 223 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (10 lines × 2) apps/openai/src/openai_chat.erl:173 — apps/openai/src/openai_chat.erl:173-182 | apps/openai/src/openai_chat.erl:301-310 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (10 lines × 2) apps/openai/src/openai_clients_sup.erl:23 — apps/openai/src/openai_clients_sup.erl:23-32 | apps/openai/src/openai_sup.erl:25-34 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (10 lines × 2) apps/openai/src/token_stream_integration.erl:290 — apps/openai/src/token_stream_integration.erl:290-299 | apps/openai/src/token_stream_integration.erl:316-325 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (10 lines × 2) apps/agent_web/src/crash_report_api_handler.erl:209 — apps/agent_web/src/crash_report_api_handler.erl:209-218 | apps/agent_web/src/crash_report_ws_handler.erl:183-192 — before extracting anything, compare `apps/agent_web/src/crash_report_api_handler.erl` and `apps/agent_web/src/crash_report_ws_handler.erl` as WHOLE FILES: this scan already matched 5 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (10 lines × 2) apps/agent_web/src/mcp_streamable_http_handler.erl:400 — apps/agent_web/src/mcp_streamable_http_handler.erl:400-409 | apps/agent_web/src/mcp_transport_streamable_http.erl:230-239 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×9
  • Members sharing a duplicated core (4 members, 50+ identical tokens) apps/agent_web/src/agent_api_handler.erl:209 — apps/agent_web/src/agent_api_handler.erl:209-264 | apps/agent_web/src/agent_chat_handler.erl:45-127 | apps/agent_web/src/bulk_operations_handler.erl:12-38 | apps/agent_web/src/workflow_api_handler.erl:9-39 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) apps/agent_web/src/mcp_cli.erl:253 — apps/agent_web/src/mcp_cli.erl:253-266 | apps/agent_web/src/mcp_cli.erl:268-279 | apps/agent_web/src/mcp_cli.erl:309-322 | apps/agent_web/src/mcp_cli.erl:324-335 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) apps/agent_web/src/mcp_management_handler.erl:162 — apps/agent_web/src/mcp_management_handler.erl:162-188 | apps/agent_web/src/mcp_management_handler.erl:220-254 | apps/agent_web/src/mcp_management_handler.erl:257-291 | apps/agent_web/src/mcp_management_handler.erl:294-328 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) apps/agent_web/src/model_api_handler.erl:103 — apps/agent_web/src/model_api_handler.erl:103-133 | apps/agent_web/src/model_api_handler.erl:224-287 | apps/agent_web/src/model_api_handler.erl:302-341 | apps/agent_web/src/model_api_handler.erl:492-535 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) apps/agents/src/agent.erl:625 — apps/agents/src/agent.erl:625-638 | apps/agents/src/simple_agent.erl:133-146 | sandbox/myapp/apps/myapp/src/agent.erl:208-221 | sandbox/myapp/apps/myapp/src/simple_agent.erl:102-115 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) apps/agents/src/agent_discovery.erl:383 — apps/agents/src/agent_discovery.erl:383-405 | apps/agents/src/agent_discovery.erl:408-455 | sandbox/myapp/apps/myapp/src/agent_discovery.erl:399-421 | sandbox/myapp/apps/myapp/src/agent_discovery.erl:424-471 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) apps/agents/src/agent_discovery.erl:471 — apps/agents/src/agent_discovery.erl:471-517 | apps/agents/src/agent_discovery.erl:520-554 | sandbox/myapp/apps/myapp/src/agent_discovery.erl:487-533 | sandbox/myapp/apps/myapp/src/agent_discovery.erl:536-570 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) apps/agents/src/simple_agent.erl:47 — apps/agents/src/simple_agent.erl:47-65 | apps/agents/src/simple_agent.erl:74-90 | sandbox/myapp/apps/myapp/src/simple_agent.erl:36-54 | sandbox/myapp/apps/myapp/src/simple_agent.erl:63-79 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) apps/openapi_scaffold/src/openapi_advanced_codegen.erl:238 — apps/openapi_scaffold/src/openapi_advanced_codegen.erl:238-253 | apps/openapi_scaffold/src/openapi_advanced_codegen.erl:365-380 | apps/openapi_scaffold/src/openapi_advanced_codegen.erl:628-643 | apps/openapi_scaffold/src/openapi_advanced_codegen.erl:923-939 — 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 · Duplicated block (13 lines × 2) · ×7
  • Duplicated block (13 lines × 2) apps/agent_web/src/agent_api_handler.erl:211 — apps/agent_web/src/agent_api_handler.erl:211-223 | apps/agent_web/src/agent_chat_handler.erl:49-61 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (13 lines × 2) apps/agent_web/src/consciousness_bridge_api_handler.erl:23 — apps/agent_web/src/consciousness_bridge_api_handler.erl:23-35 | apps/agent_web/src/neural_swarm_api_handler.erl:23-35 — before extracting anything, compare `apps/agent_web/src/consciousness_bridge_api_handler.erl` and `apps/agent_web/src/neural_swarm_api_handler.erl` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (13 lines × 2) apps/agents/src/agent_dynamic_system.erl:167 — apps/agents/src/agent_dynamic_system.erl:167-179 | apps/agents/src/dynamic_supervisor_manager.erl:139-151 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (13 lines × 2) apps/agents/src/agent_messenger.erl:185 — apps/agents/src/agent_messenger.erl:185-197 | sandbox/myapp/apps/myapp/src/agent_messenger.erl:185-197 — before extracting anything, compare `apps/agents/src/agent_messenger.erl` and `sandbox/myapp/apps/myapp/src/agent_messenger.erl` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 97 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (13 lines × 2) apps/agents/src/deep_code_reflection_engine.erl:139 — apps/agents/src/deep_code_reflection_engine.erl:139-151 | apps/agents/src/metacognitive_code_analyzer.erl:232-244 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (13 lines × 2) apps/agents/src/jina_tools.erl:466 — apps/agents/src/jina_tools.erl:466-478 | apps/agents/src/jina_tools.erl:504-516 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (13 lines × 2) apps/openapi_scaffold/src/openapi_validator.erl:131 — apps/openapi_scaffold/src/openapi_validator.erl:131-143 | apps/openapi_scaffold/src/openapi_validator.erl:178-190 — 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.
AC2 · Forms & labels · <Textarea> field component without a label · ×6
  • <Textarea> field component without a label apps/agent_web/frontend/src/components/ErrorInterpretationPanel.tsx:288 — 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.
  • <Textarea> field component without a label apps/agent_web/frontend/src/components/FleetManagementDashboard.tsx:380 — 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.
  • <Textarea> field component without a label apps/agent_web/frontend/src/components/FleetManagementDashboard.tsx:408 — 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.
  • <Textarea> field component without a label apps/agent_web/frontend/src/components/InteractiveReasoningControls.tsx:255 — 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.
  • <Textarea> field component without a label apps/agent_web/frontend/src/components/InteractiveReasoningControls.tsx:341 — 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.
  • <Textarea> field component without a label apps/agent_web/frontend/src/components/InteractiveReasoningControls.tsx:353 — 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.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×6
  • Duplicated block (14 lines × 2) apps/agent_web/src/agent_scheduling_handler.erl:103 — apps/agent_web/src/agent_scheduling_handler.erl:103-116 | apps/agent_web/src/agent_scheduling_handler.erl:177-190 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (14 lines × 2) apps/agents/src/agent.erl:609 — apps/agents/src/agent.erl:609-622 | sandbox/myapp/apps/myapp/src/agent.erl:192-205 — before extracting anything, compare `apps/agents/src/agent.erl` and `sandbox/myapp/apps/myapp/src/agent.erl` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 154 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (14 lines × 2) apps/agents/src/timeline_event_store.erl:411 — apps/agents/src/timeline_event_store.erl:411-424 | apps/agents/src/timeline_event_store.erl:444-457 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (14 lines × 2) apps/openai/src/openai_chat.erl:158 — apps/openai/src/openai_chat.erl:158-171 | apps/openai/src/openai_chat.erl:286-299 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (14 lines × 2) apps/openai/src/token_stream_fsm.erl:198 — apps/openai/src/token_stream_fsm.erl:198-211 | apps/openai/src/token_stream_fsm.erl:216-229 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (14 lines × 2) apps/agent_web/src/mcp_health_handler.erl:93 — apps/agent_web/src/mcp_health_handler.erl:93-106 | apps/agent_web/src/mcp_health_handler.erl:161-174 — 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.
AC1 · Text alternatives · <canvas> without a text alternative · ×5
  • <canvas> without a text alternative apps/agent_web/frontend/src/components/ChainOfThoughtVisualization.tsx:331 — 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 apps/agent_web/frontend/src/components/QuantumConsciousnessInterface.tsx:371 — 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 apps/agent_web/frontend/src/components/UltraAdvancedDashboard.tsx:276 — 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 apps/agent_web/frontend/src/components/UltraAdvancedDashboard.tsx:355 — 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 apps/agent_web/frontend/src/components/UltraAdvancedDashboard.tsx:468 — 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.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×5
  • Duplicated block (16 lines × 2) apps/agent_web/src/crash_report_api_handler.erl:249 — apps/agent_web/src/crash_report_api_handler.erl:249-264 | apps/agent_web/src/crash_report_ws_handler.erl:217-232 — before extracting anything, compare `apps/agent_web/src/crash_report_api_handler.erl` and `apps/agent_web/src/crash_report_ws_handler.erl` as WHOLE FILES: this scan already matched 5 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (16 lines × 2) apps/agent_web/src/mcp_transport.erl:167 — apps/agent_web/src/mcp_transport.erl:167-182 | apps/agent_web/src/mcp_transport.erl:226-241 — 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 (16 lines × 2) apps/agents/src/agent.erl:650 — apps/agents/src/agent.erl:650-665 | sandbox/myapp/apps/myapp/src/agent.erl:233-248 — before extracting anything, compare `apps/agents/src/agent.erl` and `sandbox/myapp/apps/myapp/src/agent.erl` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 154 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (16 lines × 2) apps/agents/src/agent.erl:692 — apps/agents/src/agent.erl:692-707 | sandbox/myapp/apps/myapp/src/agent.erl:275-290 — before extracting anything, compare `apps/agents/src/agent.erl` and `sandbox/myapp/apps/myapp/src/agent.erl` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 154 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (16 lines × 2) apps/openai/src/anthropic_client_template.erl:157 — apps/openai/src/anthropic_client_template.erl:157-172 | apps/openai/src/openai_client_template.erl:151-166 — before extracting anything, compare `apps/openai/src/anthropic_client_template.erl` and `apps/openai/src/openai_client_template.erl` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×5
  • Duplicated block (15 lines × 2) apps/agent_web/src/bulk_operations_handler.erl:12 — apps/agent_web/src/bulk_operations_handler.erl:12-26 | apps/agent_web/src/workflow_api_handler.erl:9-23 — before extracting anything, compare `apps/agent_web/src/bulk_operations_handler.erl` and `apps/agent_web/src/workflow_api_handler.erl` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (15 lines × 2) apps/agent_web/src/pipedream_mcp_client.erl:208 — apps/agent_web/src/pipedream_mcp_client.erl:208-222 | apps/agent_web/src/pipedream_mcp_client.erl:249-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.
  • Duplicated block (15 lines × 2) apps/agents/src/agent_protocol.erl:107 — apps/agents/src/agent_protocol.erl:107-121 | sandbox/myapp/apps/myapp/src/agent_protocol.erl:114-128 — before extracting anything, compare `apps/agents/src/agent_protocol.erl` and `sandbox/myapp/apps/myapp/src/agent_protocol.erl` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (15 lines × 2) apps/openai/src/openai_responses.erl:289 — apps/openai/src/openai_responses.erl:289-303 | apps/openai/src/openai_responses.erl:386-400 — 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 (15 lines × 2) apps/openai/src/token_stream_integration.erl:211 — apps/openai/src/token_stream_integration.erl:211-225 | apps/openai/src/token_stream_integration.erl:229-243 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×4
  • Duplicated block (17 lines × 2) apps/agent_web/src/model_api_handler.erl:178 — apps/agent_web/src/model_api_handler.erl:178-194 | apps/agent_web/src/model_api_handler.erl:256-272 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (17 lines × 2) apps/agents/src/agent.erl:673 — apps/agents/src/agent.erl:673-689 | sandbox/myapp/apps/myapp/src/agent.erl:256-272 — before extracting anything, compare `apps/agents/src/agent.erl` and `sandbox/myapp/apps/myapp/src/agent.erl` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 154 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (17 lines × 2) apps/agents/src/simple_agent.erl:74 — apps/agents/src/simple_agent.erl:74-90 | sandbox/myapp/apps/myapp/src/simple_agent.erl:63-79 — before extracting anything, compare `apps/agents/src/simple_agent.erl` and `sandbox/myapp/apps/myapp/src/simple_agent.erl` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (17 lines × 2) examples/advanced_distributed_agents.erl:316 — examples/advanced_distributed_agents.erl:316-332 | examples/advanced_tool_composition.erl:424-440 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (10 lines × 3) · ×4
  • Duplicated block (10 lines × 3) apps/agent_web/src/mcp_server.erl:381 — apps/agent_web/src/mcp_server.erl:381-390 | apps/agents/src/agent_tools.erl:2043-2052 | apps/agents/src/jina_tools.erl:171-180 — before extracting anything, compare `apps/agent_web/src/mcp_server.erl` and `apps/agents/src/agent_tools.erl` 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.
  • Duplicated block (10 lines × 3) apps/agents/src/agent_tools.erl:164 — apps/agents/src/agent_tools.erl:164-173 | apps/agents/src/agent_tools.erl:221-230 | sandbox/myapp/apps/myapp/src/agent_tools.erl:122-131 — before extracting anything, compare `apps/agents/src/agent_tools.erl` and `sandbox/myapp/apps/myapp/src/agent_tools.erl` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 223 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (10 lines × 3) apps/agent_web/src/mcp_management_handler.erl:64 — apps/agent_web/src/mcp_management_handler.erl:64-73 | apps/agent_web/src/mcp_management_handler.erl:99-108 | apps/agent_web/src/mcp_management_handler.erl:146-155 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (10 lines × 3) apps/agent_web/src/mcp_server.erl:696 — apps/agent_web/src/mcp_server.erl:696-705 | apps/agent_web/src/mcp_server.erl:766-775 | apps/agent_web/src/mcp_server.erl:829-838 — 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.
R10 · Code Duplication · Duplicated block (16 lines × 2 locations) · ×4
  • Duplicated block (16 lines × 2 locations) apps/agent_web/frontend/src/components/MCPServerManager.tsx:143 — apps/agent_web/frontend/src/components/MCPServerManager.tsx:143 · apps/agent_web/frontend/src/components/MCPServerManager.tsx:173 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
  • Duplicated block (16 lines × 2 locations) apps/agent_web/frontend/src/components/ResourceSentinelBar.tsx:100 — apps/agent_web/frontend/src/components/ResourceSentinelBar.tsx:100 · apps/agent_web/frontend/src/components/ResourceSentinelBar.tsx:119 — 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 (16 lines × 2 locations) apps/agent_web/frontend/src/components/ui/select.tsx:33 — apps/agent_web/frontend/src/components/ui/select.tsx:33 · apps/agent_web/frontend/src/components/ui/select.tsx:50 — all 2 copies are in the same file, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.
  • Duplicated block (16 lines × 2 locations) REDACTED:1787 — REDACTED:1787 · REDACTED:1869 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (14 lines × 2 locations) · ×4
  • Duplicated block (14 lines × 2 locations) apps/agent_web/frontend/src/components/ApiKeyManager.tsx:333 — apps/agent_web/frontend/src/components/ApiKeyManager.tsx:333 · apps/agent_web/frontend/src/components/FleetManagementDashboard.tsx:391 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
  • Duplicated block (14 lines × 2 locations) apps/agent_web/frontend/src/components/CommandPalette.tsx:124 — apps/agent_web/frontend/src/components/CommandPalette.tsx:124 · apps/agent_web/frontend/src/components/CommandPalette.tsx:187 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (14 lines × 2 locations) REDACTED:84 — REDACTED:84 · REDACTED:178 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (14 lines × 2 locations) apps/agent_web/frontend/src/components/RightDrawerInspector.tsx:192 — apps/agent_web/frontend/src/components/RightDrawerInspector.tsx:192 · apps/agent_web/frontend/src/components/RightDrawerInspector.tsx:230 — 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.
AC3 · Page structure · Heading level jumps from h1 to h3 · ×3
  • Heading level jumps from h1 to h3 apps/agent_web/frontend/src/components/CrashMonitorDashboard.tsx:488 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
  • Heading level jumps from h1 to h3 apps/agent_web/frontend/src/components/MainLayoutWithSidebar.tsx:228 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
  • Heading level jumps from h1 to h3 apps/agent_web/frontend/src/components/ToolRegistry.tsx:490 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
D30 · Dependency Vulnerabilities · Medium CVE · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (30 lines × 2) · ×3
  • Duplicated block (30 lines × 2) apps/agent_web/src/mcp_client_v2.erl:129 — apps/agent_web/src/mcp_client_v2.erl:129-158 | apps/agent_web/src/mcp_client_v2.erl:165-194 — 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) apps/agents/src/agent_messenger.erl:153 — apps/agents/src/agent_messenger.erl:153-182 | sandbox/myapp/apps/myapp/src/agent_messenger.erl:153-182 — before extracting anything, compare `apps/agents/src/agent_messenger.erl` and `sandbox/myapp/apps/myapp/src/agent_messenger.erl` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 97 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (30 lines × 2) apps/agents/src/agent_protocol.erl:213 — apps/agents/src/agent_protocol.erl:213-242 | sandbox/myapp/apps/myapp/src/agent_protocol.erl:220-249 — before extracting anything, compare `apps/agents/src/agent_protocol.erl` and `sandbox/myapp/apps/myapp/src/agent_protocol.erl` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 71 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.
D4 · Code Duplication · Duplicated block (20 lines × 2) · ×3
  • Duplicated block (20 lines × 2) apps/agent_web/src/mcp_oauth_integration.erl:210 — apps/agent_web/src/mcp_oauth_integration.erl:210-229 | apps/agent_web/src/mcp_oauth_integration.erl:430-449 — 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 (20 lines × 2) apps/agent_web/src/pipedream_api_handler.erl:81 — apps/agent_web/src/pipedream_api_handler.erl:81-100 | apps/agent_web/src/pipedream_api_handler.erl:110-129 — 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 (20 lines × 2) apps/agents/src/streaming_function_handler.erl:436 — apps/agents/src/streaming_function_handler.erl:436-455 | apps/openai/src/openai_streaming.erl:176-195 — 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.
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×3
  • Duplicated block (19 lines × 2) apps/agents/src/agent_instance.erl:1511 — apps/agents/src/agent_instance.erl:1511-1529 | apps/agents/src/agent_instance.erl:1546-1564 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (19 lines × 2) apps/agents/src/simple_agent.erl:47 — apps/agents/src/simple_agent.erl:47-65 | sandbox/myapp/apps/myapp/src/simple_agent.erl:36-54 — before extracting anything, compare `apps/agents/src/simple_agent.erl` and `sandbox/myapp/apps/myapp/src/simple_agent.erl` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (19 lines × 2) apps/openai/src/token_stream_fsm.erl:268 — apps/openai/src/token_stream_fsm.erl:268-286 | apps/openai/src/token_stream_fsm.erl:291-309 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (18 lines × 2) · ×3
  • Duplicated block (18 lines × 2) apps/agents/src/agent_discovery.erl:275 — apps/agents/src/agent_discovery.erl:275-292 | sandbox/myapp/apps/myapp/src/agent_discovery.erl:291-308 — before extracting anything, compare `apps/agents/src/agent_discovery.erl` and `sandbox/myapp/apps/myapp/src/agent_discovery.erl` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 382 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (18 lines × 2) apps/agents/src/agent_discovery.erl:363 — apps/agents/src/agent_discovery.erl:363-380 | sandbox/myapp/apps/myapp/src/agent_discovery.erl:379-396 — before extracting anything, compare `apps/agents/src/agent_discovery.erl` and `sandbox/myapp/apps/myapp/src/agent_discovery.erl` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 382 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (18 lines × 2) apps/openai/src/anthropic_client_template.erl:44 — apps/openai/src/anthropic_client_template.erl:44-61 | apps/openai/src/openai_client_template.erl:42-59 — before extracting anything, compare `apps/openai/src/anthropic_client_template.erl` and `apps/openai/src/openai_client_template.erl` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (16–17 lines × 2) · ×3
  • Duplicated block (16–17 lines × 2) apps/agent_web/src/agent_scheduling_handler.erl:167 — apps/agent_web/src/agent_scheduling_handler.erl:167-183 | apps/agent_web/src/agent_scheduling_handler.erl:207-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.
  • Duplicated block (16–17 lines × 2) apps/agent_web/src/mcp_client_v2.erl:399 — apps/agent_web/src/mcp_client_v2.erl:399-414 | apps/agent_web/src/mcp_client_v2.erl:502-518 — 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 (16–17 lines × 2) apps/openai/src/openai_responses.erl:216 — apps/openai/src/openai_responses.erl:216-231 | apps/openai/src/openai_responses.erl:261-277 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (9–10 lines × 2) · ×3
  • Duplicated block (9–10 lines × 2) apps/agent_web/src/mcp_server.erl:360 — apps/agent_web/src/mcp_server.erl:360-369 | apps/agents/src/jina_tools.erl:131-139 — before extracting anything, compare `apps/agent_web/src/mcp_server.erl` and `apps/agents/src/jina_tools.erl` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 62 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (9–10 lines × 2) apps/agent_web/src/pdf_processing_integration.erl:82 — apps/agent_web/src/pdf_processing_integration.erl:82-91 | apps/agent_web/src/pdf_processing_integration.erl:107-115 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (9–10 lines × 2) apps/agent_web/src/stats_control_handler.erl:11 — apps/agent_web/src/stats_control_handler.erl:11-19 | apps/agent_web/src/stats_control_handler.erl:46-55 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (9 lines × 4) · ×3
  • Duplicated block (9 lines × 4) apps/agents/src/simple_agent.erl:49 — apps/agents/src/simple_agent.erl:49-57 | apps/agents/src/simple_agent.erl:76-84 | sandbox/myapp/apps/myapp/src/simple_agent.erl:38-46 | sandbox/myapp/apps/myapp/src/simple_agent.erl:65-73 — before extracting anything, compare `apps/agents/src/simple_agent.erl` and `sandbox/myapp/apps/myapp/src/simple_agent.erl` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (9 lines × 4) apps/agent_web/src/workflow_api_handler.erl:116 — apps/agent_web/src/workflow_api_handler.erl:116-124 | apps/agent_web/src/workflow_api_handler.erl:309-317 | apps/agent_web/src/workflow_api_handler.erl:379-387 | apps/agent_web/src/workflow_api_handler.erl:411-419 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (9 lines × 4) apps/agent_web/src/agent_scheduling_handler.erl:136 — apps/agent_web/src/agent_scheduling_handler.erl:136-144 | apps/agent_web/src/agent_scheduling_handler.erl:215-223 | apps/agent_web/src/agent_scheduling_handler.erl:236-244 | apps/agent_web/src/agent_scheduling_handler.erl:278-286 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (8 lines × 4) · ×3
  • Duplicated block (8 lines × 4) apps/agent_web/src/agent_communication_handler.erl:28 — apps/agent_web/src/agent_communication_handler.erl:28-35 | apps/agent_web/src/agent_communication_handler.erl:53-60 | apps/agent_web/src/agent_quorum_handler.erl:25-32 | apps/agent_web/src/agent_quorum_handler.erl:50-57 — before extracting anything, compare `apps/agent_web/src/agent_communication_handler.erl` and `apps/agent_web/src/agent_quorum_handler.erl` as WHOLE FILES: this scan already matched 4 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (8 lines × 4) apps/agent_web/src/model_api_handler.erl:119 — apps/agent_web/src/model_api_handler.erl:119-126 | apps/agent_web/src/model_api_handler.erl:244-251 | apps/agent_web/src/model_api_handler.erl:315-322 | apps/agent_web/src/model_api_handler.erl:509-516 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (8 lines × 4) apps/agents/src/agent_tools.erl:1852 — apps/agents/src/agent_tools.erl:1852-1859 | apps/agents/src/agent_tools.erl:1892-1899 | apps/agents/src/jina_tools.erl:19-26 | apps/agents/src/jina_tools.erl:55-62 — before extracting anything, compare `apps/agents/src/agent_tools.erl` and `apps/agents/src/jina_tools.erl` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 201 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (7 lines × 3) · ×3
  • Duplicated block (7 lines × 3) apps/agent_web/src/ai_error_interpreter.erl:419 — apps/agent_web/src/ai_error_interpreter.erl:419-425 | apps/agent_web/src/crash_report_api_handler.erl:232-238 | apps/agent_web/src/crash_report_ws_handler.erl:206-212 — before extracting anything, compare `apps/agent_web/src/crash_report_api_handler.erl` and `apps/agent_web/src/crash_report_ws_handler.erl` as WHOLE FILES: this scan already matched 5 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (7 lines × 3) apps/agent_web/src/consciousness_bridge_api_handler.erl:151 — apps/agent_web/src/consciousness_bridge_api_handler.erl:151-157 | apps/agent_web/src/neural_swarm_api_handler.erl:138-144 | apps/agent_web/src/neural_swarm_api_handler.erl:189-195 — before extracting anything, compare `apps/agent_web/src/consciousness_bridge_api_handler.erl` and `apps/agent_web/src/neural_swarm_api_handler.erl` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (7 lines × 3) apps/agent_web/src/mcp_server_handler.erl:118 — apps/agent_web/src/mcp_server_handler.erl:118-124 | apps/agent_web/src/mcp_server_handler.erl:141-147 | apps/agent_web/src/mcp_server_handler.erl:186-192 — 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.
D4 · Code Duplication · Duplicated block (6 lines × 4) · ×3
  • Duplicated block (6 lines × 4) apps/agent_web/src/agent_communication_handler.erl:22 — apps/agent_web/src/agent_communication_handler.erl:22-27 | apps/agent_web/src/agent_communication_handler.erl:47-52 | apps/agent_web/src/agent_quorum_handler.erl:19-24 | apps/agent_web/src/agent_quorum_handler.erl:44-49 — before extracting anything, compare `apps/agent_web/src/agent_communication_handler.erl` and `apps/agent_web/src/agent_quorum_handler.erl` as WHOLE FILES: this scan already matched 4 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (6 lines × 4) apps/agent_web/src/mcp_cli.erl:259 — apps/agent_web/src/mcp_cli.erl:259-264 | apps/agent_web/src/mcp_cli.erl:272-277 | apps/agent_web/src/mcp_cli.erl:315-320 | apps/agent_web/src/mcp_cli.erl:328-333 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (6 lines × 4) apps/agent_web/src/model_api_handler.erl:69 — apps/agent_web/src/model_api_handler.erl:69-74 | apps/agent_web/src/model_api_handler.erl:141-146 | apps/agent_web/src/model_api_handler.erl:215-220 | apps/agent_web/src/model_api_handler.erl:293-298 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
ED2 · Event/command shape · Command with competing owners · ×3
  • Command with competing owners: create_swarm apps/agents/src/cluster_orchestrator.erl:138 — `create_swarm` is shaped like a command (one imperative intent) but is handled synchronously by more than one module — a command should have exactly one owning handler. Split the responsibilities, or raise an EVENT after the command and let the others subscribe.
  • Command with competing owners: create_swarm apps/agents/src/emergent_swarm_intelligence.erl:237 — `create_swarm` is shaped like a command (one imperative intent) but is handled synchronously by more than one module — a command should have exactly one owning handler. Split the responsibilities, or raise an EVENT after the command and let the others subscribe.
  • Command with competing owners: create_swarm apps/agents/src/swarm_intelligence_engine.erl:131 — `create_swarm` is shaped like a command (one imperative intent) but is handled synchronously by more than one module — a command should have exactly one owning handler. Split the responsibilities, or raise an EVENT after the command and let the others subscribe.
R10 · Code Duplication · Duplicated block (17 lines × 2 locations) · ×3
  • Duplicated block (17 lines × 2 locations) apps/agent_web/frontend/src/components/CrashMonitorDashboard.tsx:442 — apps/agent_web/frontend/src/components/CrashMonitorDashboard.tsx:442 · apps/agent_web/frontend/src/components/ErrorInterpretationPanel.tsx:352 — 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 (17 lines × 2 locations) apps/agent_web/frontend/src/components/MCPOAuthManager.tsx:148 — apps/agent_web/frontend/src/components/MCPOAuthManager.tsx:148 · apps/agent_web/frontend/src/components/MCPOAuthManager.tsx:170 — 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 (17 lines × 2 locations) apps/agent_web/frontend/src/components/MultiAgentChat.tsx:483 — apps/agent_web/frontend/src/components/MultiAgentChat.tsx:483 · REDACTED:1009 — 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 (15 lines × 2 locations) · ×3
  • Duplicated block (15 lines × 2 locations) apps/agent_web/frontend/src/components/MCPOrchestrationEngine.tsx:587 — apps/agent_web/frontend/src/components/MCPOrchestrationEngine.tsx:587 · apps/agent_web/frontend/src/components/MCPOrchestrationEngine.tsx:604 — 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 (15 lines × 2 locations) apps/agent_web/frontend/src/components/PipedreamConnectionManager.tsx:83 — apps/agent_web/frontend/src/components/PipedreamConnectionManager.tsx:83 · apps/agent_web/frontend/src/components/PipedreamConnectionManager.tsx:99 — 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 (15 lines × 2 locations) apps/agent_web/frontend/src/components/PipedreamConnectionManager.tsx:128 — apps/agent_web/frontend/src/components/PipedreamConnectionManager.tsx:128 · apps/agent_web/frontend/src/components/PipedreamConnectionManager.tsx:152 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (13 lines × 2 locations) · ×3
  • Duplicated block (13 lines × 2 locations) REDACTED:466 — REDACTED:466 · apps/agent_web/frontend/src/components/OAuthManager.tsx:299 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (13 lines × 2 locations) apps/agent_web/frontend/src/components/ComprehensiveMCPManager.tsx:877 — apps/agent_web/frontend/src/components/ComprehensiveMCPManager.tsx:877 · apps/agent_web/frontend/src/components/ComprehensiveMCPManager.tsx:891 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (13 lines × 2 locations) REDACTED:974 — REDACTED:974 · REDACTED:990 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
AC3 · Page structure · Heading level jumps from h1 to h4 · ×2
  • Heading level jumps from h1 to h4 apps/agent_web/frontend/src/components/DiscoveryMeshDashboard.tsx:359 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
  • Heading level jumps from h1 to h4 apps/agent_web/frontend/src/components/UltraAdvancedDashboard.tsx:780 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
AC6 · Visual & motion safety · Low contrast Tailwind colour pair (3.8 · ×2
  • Low contrast Tailwind colour pair (3.8:1) apps/agent_web/frontend/src/components/DynamicUIManager.tsx:506 — This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
  • Low contrast Tailwind colour pair (3.8:1) apps/agent_web/frontend/src/components/DynamicUIManager.tsx:548 — This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (4.4 · ×2
  • Low contrast colour pair in CSS (4.4:1) apps/agent_web/priv/static/css/style.css:186 — `.agent-item.active` sets color: white on background-color: #6366f1 — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (4.4:1) apps/agent_web/priv/static/css/style.css:296 — `.btn-primary` sets color: white on background-color: #6366f1 — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
D3 · God Classes · TooManyMethods · ×2
  • TooManyMethods: ChainOfThoughtEngine apps/agent_web/frontend/src/services/ChainOfThoughtEngine.ts:74 — TooManyMethods — 38 methods. The bar is 30 methods; this is 8 over it, 1.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: CollaborationManager apps/agent_web/frontend/src/services/CollaborationManager.ts:126 — TooManyMethods — 36 methods. The bar is 30 methods; this is 6 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication · Duplicated block (48 lines × 2) · ×2
  • Duplicated block (48 lines × 2) apps/agents/src/agent.erl:549 — apps/agents/src/agent.erl:549-596 | sandbox/myapp/apps/myapp/src/agent.erl:132-179 — before extracting anything, compare `apps/agents/src/agent.erl` and `sandbox/myapp/apps/myapp/src/agent.erl` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 154 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (48 lines × 2) apps/agents/src/agent_discovery.erl:408 — apps/agents/src/agent_discovery.erl:408-455 | sandbox/myapp/apps/myapp/src/agent_discovery.erl:424-471 — before extracting anything, compare `apps/agents/src/agent_discovery.erl` and `sandbox/myapp/apps/myapp/src/agent_discovery.erl` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 382 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.
D4 · Code Duplication · Duplicated block (24–25 lines × 2) · ×2
  • Duplicated block (24–25 lines × 2) apps/agents/src/agent_tools.erl:105 — apps/agents/src/agent_tools.erl:105-128 | sandbox/myapp/apps/myapp/src/agent_tools.erl:65-89 — before extracting anything, compare `apps/agents/src/agent_tools.erl` and `sandbox/myapp/apps/myapp/src/agent_tools.erl` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 223 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (24–25 lines × 2) apps/agents/src/agent_tools.erl:1927 — apps/agents/src/agent_tools.erl:1927-1950 | apps/agents/src/jina_tools.erl:86-110 — before extracting anything, compare `apps/agents/src/agent_tools.erl` and `apps/agents/src/jina_tools.erl` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 201 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (21 lines × 2) · ×2
  • Duplicated block (21 lines × 2) apps/openai/src/anthropic_client_template.erl:95 — apps/openai/src/anthropic_client_template.erl:95-115 | apps/openai/src/openai_client_template.erl:91-111 — before extracting anything, compare `apps/openai/src/anthropic_client_template.erl` and `apps/openai/src/openai_client_template.erl` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (21 lines × 2) apps/openai/src/openai_completions.erl:45 — apps/openai/src/openai_completions.erl:45-65 | apps/openai/src/openai_embeddings.erl:45-65 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (17–18 lines × 2) · ×2
  • Duplicated block (17–18 lines × 2) apps/agents/src/agent_tools.erl:1852 — apps/agents/src/agent_tools.erl:1852-1868 | apps/agents/src/jina_tools.erl:19-36 — before extracting anything, compare `apps/agents/src/agent_tools.erl` and `apps/agents/src/jina_tools.erl` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 201 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (17–18 lines × 2) apps/agents/src/agent_tools.erl:1892 — apps/agents/src/agent_tools.erl:1892-1908 | apps/agents/src/jina_tools.erl:55-72 — before extracting anything, compare `apps/agents/src/agent_tools.erl` and `apps/agents/src/jina_tools.erl` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 201 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (14–15 lines × 3) · ×2
  • Duplicated block (14–15 lines × 3) apps/agent_web/src/mcp_server.erl:298 — apps/agent_web/src/mcp_server.erl:298-312 | apps/agents/src/agent_tools.erl:1852-1865 | apps/agents/src/jina_tools.erl:19-32 — before extracting anything, compare `apps/agent_web/src/mcp_server.erl` and `apps/agents/src/agent_tools.erl` 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.
  • Duplicated block (14–15 lines × 3) apps/agent_web/src/mcp_server.erl:406 — apps/agent_web/src/mcp_server.erl:406-420 | apps/agents/src/agent_tools.erl:2074-2087 | apps/agents/src/jina_tools.erl:200-213 — before extracting anything, compare `apps/agent_web/src/mcp_server.erl` and `apps/agents/src/agent_tools.erl` 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.
D4 · Code Duplication · Duplicated block (13–14 lines × 2) · ×2
  • Duplicated block (13–14 lines × 2) apps/agents/src/agent_tools.erl:362 — apps/agents/src/agent_tools.erl:362-374 | sandbox/myapp/apps/myapp/src/agent_tools.erl:203-216 — before extracting anything, compare `apps/agents/src/agent_tools.erl` and `sandbox/myapp/apps/myapp/src/agent_tools.erl` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 223 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (13–14 lines × 2) apps/agents/src/jina_tools.erl:28 — apps/agents/src/jina_tools.erl:28-40 | apps/agents/src/jina_tools.erl:64-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.
D4 · Code Duplication · Duplicated block (9–10 lines × 3) · ×2
  • Duplicated block (9–10 lines × 3) apps/agent_web/src/examples_handler.erl:13 — apps/agent_web/src/examples_handler.erl:13-21 | apps/agent_web/src/knowledge_base_handler.erl:122-131 | apps/agent_web/src/knowledge_base_handler.erl:144-153 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
  • Duplicated block (9–10 lines × 3) apps/agent_web/src/mcp_sse_handler.erl:167 — apps/agent_web/src/mcp_sse_handler.erl:167-175 | apps/agent_web/src/mcp_sse_handler.erl:185-194 | apps/agent_web/src/mcp_sse_handler.erl:204-213 — 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.
D4 · Code Duplication · Duplicated block (8–10 lines × 2) · ×2
  • Duplicated block (8–10 lines × 2) apps/agents/src/agent_tools.erl:2838 — apps/agents/src/agent_tools.erl:2838-2845 | apps/agents/src/agent_tools.erl:2925-2934 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (8–10 lines × 2) apps/agents/src/quantum_consciousness_engine.erl:537 — apps/agents/src/quantum_consciousness_engine.erl:537-544 | apps/agents/src/quantum_consciousness_engine.erl:548-557 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (8 lines × 3) · ×2
  • Duplicated block (8 lines × 3) apps/agent_web/src/mcp_orchestration_handler.erl:19 — apps/agent_web/src/mcp_orchestration_handler.erl:19-26 | apps/agent_web/src/mcp_orchestration_handler.erl:32-39 | apps/agent_web/src/mcp_orchestration_handler.erl:173-180 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (8 lines × 3) apps/agent_web/src/pipedream_api_handler.erl:47 — apps/agent_web/src/pipedream_api_handler.erl:47-54 | apps/agent_web/src/pipedream_api_handler.erl:90-97 | apps/agent_web/src/pipedream_api_handler.erl:119-126 — 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.
D4 · Code Duplication · Duplicated block (5 lines × 4) · ×2
  • Duplicated block (5 lines × 4) apps/openapi_scaffold/src/openapi_advanced_codegen.erl:239 — apps/openapi_scaffold/src/openapi_advanced_codegen.erl:239-243 | apps/openapi_scaffold/src/openapi_advanced_codegen.erl:366-370 | apps/openapi_scaffold/src/openapi_advanced_codegen.erl:629-633 | apps/openapi_scaffold/src/openapi_advanced_codegen.erl:924-928 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (5 lines × 4) apps/agent_web/src/conversation_handler.erl:114 — apps/agent_web/src/conversation_handler.erl:114-118 | apps/agent_web/src/conversation_handler.erl:123-127 | apps/agent_web/src/conversation_handler.erl:150-154 | apps/agent_web/src/conversation_handler.erl:210-214 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (5 lines × 3) · ×2
  • Duplicated block (5 lines × 3) apps/agent_web/src/conversation_handler.erl:114 — apps/agent_web/src/conversation_handler.erl:114-118 | apps/agent_web/src/conversation_handler.erl:150-154 | apps/agent_web/src/conversation_handler.erl:210-214 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (5 lines × 3) apps/agent_web/src/bulk_operations_handler.erl:79 — apps/agent_web/src/bulk_operations_handler.erl:79-84 | apps/agent_web/src/bulk_operations_handler.erl:226-231 | apps/agent_web/src/bulk_operations_handler.erl:278-282 — 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.
R10 · Code Duplication · Duplicated block (22 lines × 2 locations) · ×2
  • Duplicated block (22 lines × 2 locations) apps/agent_web/frontend/src/components/AdaptiveAIInterface.tsx:367 — apps/agent_web/frontend/src/components/AdaptiveAIInterface.tsx:367 · apps/agent_web/frontend/src/components/QuantumConsciousnessInterface.tsx:376 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
  • Duplicated block (22 lines × 2 locations) apps/agent_web/frontend/src/components/CrashMonitorDashboard.tsx:319 — apps/agent_web/frontend/src/components/CrashMonitorDashboard.tsx:319 · apps/agent_web/frontend/src/components/ErrorInterpretationPanel.tsx:230 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication · Duplicated block (19 lines × 2 locations) · ×2
  • Duplicated block (19 lines × 2 locations) apps/agent_web/frontend/src/components/CrashMonitorDashboard.tsx:414 — apps/agent_web/frontend/src/components/CrashMonitorDashboard.tsx:414 · apps/agent_web/frontend/src/components/ErrorInterpretationPanel.tsx:319 — 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 (19 lines × 2 locations) apps/agent_web/frontend/src/components/InteractiveReasoningControls.tsx:392 — apps/agent_web/frontend/src/components/InteractiveReasoningControls.tsx:392 · apps/agent_web/frontend/src/components/InteractiveReasoningControls.tsx:453 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication · Duplicated block (12 lines × 2 locations) · ×2
  • Duplicated block (12 lines × 2 locations) apps/agent_web/frontend/src/components/AdaptiveAIInterface.tsx:467 — apps/agent_web/frontend/src/components/AdaptiveAIInterface.tsx:467 · apps/agent_web/frontend/src/components/AdaptiveAIInterface.tsx:480 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (12 lines × 2 locations) apps/agent_web/frontend/src/components/AdvancedMessageRenderer.tsx:225 — apps/agent_web/frontend/src/components/AdvancedMessageRenderer.tsx:225 · apps/agent_web/frontend/src/components/AdvancedMessageRenderer.tsx:259 — 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.
AC3 · Page structure · Heading level jumps from h2 to h4 · ×1
  • Heading level jumps from h2 to h4 REDACTED:1421 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
AC6 · Visual & motion safety · Low contrast Tailwind colour pair (3.3 · ×1
  • Low contrast Tailwind colour pair (3.3:1) apps/agent_web/frontend/src/components/MCPServerManager.tsx:196 — This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
AC6 · Visual & motion safety · Low contrast Tailwind colour pair (3.1 · ×1
  • Low contrast Tailwind colour pair (3.1:1) apps/agent_web/frontend/src/components/MultiAgentChat.tsx:236 — This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
AC6 · Visual & motion safety · Low contrast Tailwind colour pair (2.3 · ×1
  • Low contrast Tailwind colour pair (2.3:1) apps/agent_web/frontend/src/components/NetworkTopology.tsx:136 — This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (2.5 · ×1
  • Low contrast colour pair in CSS (2.5:1) apps/agent_web/priv/static/css/style.css:305 — `.btn-success` sets color: white on background-color: #10b981 — 2.5:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (3.8 · ×1
  • Low contrast colour pair in CSS (3.8:1) apps/agent_web/priv/static/css/style.css:314 — `.btn-danger` sets color: white on background-color: #ef4444 — 3.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (3.2 · ×1
  • Low contrast colour pair in CSS (3.2:1) apps/agent_web/priv/static/css/style.css:785 — `.node` sets color: white on background-color: #3498db — 3.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC7 · A11y enforcement · Accessibility enforcement below the top rung · ×1
  • Accessibility enforcement below the top rung apps/agent_web/frontend/package.json:47 — No accessibility enforcement found — no a11y linter (eslint-plugin-jsx-a11y) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 78 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
D1 · Cyclomatic Complexity · AdvancedMCPDashboard.AdvancedMCPDashboard (cyclomatic 113) · ×1
  • AdvancedMCPDashboard.AdvancedMCPDashboard (cyclomatic 113) REDACTED:157 — AdvancedMCPDashboard.AdvancedMCPDashboard has cyclomatic complexity 113 (threshold 15). Most of this is not in the body itself: 7 of the 113 points are its own statements and the rest belongs to 35 function items inside it that branch (ServerDetails, a function literal at line 321, disconnectServer, …). 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.
D1 · Cyclomatic Complexity · SimpleAdvancedChat.SimpleAdvancedChat (cyclomatic 104) · ×1
  • SimpleAdvancedChat.SimpleAdvancedChat (cyclomatic 104) REDACTED:384 — SimpleAdvancedChat.SimpleAdvancedChat has cyclomatic complexity 104 (threshold 15). Of this number, 17 points are the body's own statements and 87 belong to 24 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.
D1 · Cyclomatic Complexity · agent_tools.predefined_executor (cyclomatic 85) · ×1
  • agent_tools.predefined_executor (cyclomatic 85) apps/agents/src/agent_tools.erl:1319 — agent_tools.predefined_executor has cyclomatic complexity 85 (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.
D1 · Cyclomatic Complexity · hyper_graph_storage.handle_call (cyclomatic 73) · ×1
  • hyper_graph_storage.handle_call (cyclomatic 73) apps/agent_web/src/hyper_graph_storage.erl:125 — hyper_graph_storage.handle_call has cyclomatic complexity 73 (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.
D1 · Cyclomatic Complexity · embedding_integration.handle_call (cyclomatic 70) · ×1
  • embedding_integration.handle_call (cyclomatic 70) apps/agent_web/src/embedding_integration.erl:86 — embedding_integration.handle_call has cyclomatic complexity 70 (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.
D1 · Cyclomatic Complexity · App.App (cyclomatic 69) · ×1
  • App.App (cyclomatic 69) apps/agent_web/frontend/src/App.tsx:55 — App.App has cyclomatic complexity 69 (threshold 15). Most of this is not in the body itself: 5 of the 69 points are its own statements and the rest belongs to 14 function items inside it that branch (a function literal at line 226, handleExecuteAction, loadSystemMetrics, …). 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.
D1 · Cyclomatic Complexity · Timeline.Timeline (cyclomatic 64) · ×1
  • Timeline.Timeline (cyclomatic 64) apps/agent_web/frontend/src/components/Timeline.tsx:59 — Timeline.Timeline has cyclomatic complexity 64 (threshold 15). Most of this is not in the body itself: 4 of the 64 points are its own statements and the rest belongs to 15 function items inside it that branch (handleWebSocketEvent, a function literal at line 492, a function literal at line 297, …). 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.
D1 · Cyclomatic Complexity · SystemMonitoringDashboard.SystemMonitoringDashboard (cyclomatic 62) · ×1
  • SystemMonitoringDashboard.SystemMonitoringDashboard (cyclomatic 62) apps/agent_web/frontend/src/components/SystemMonitoringDashboard.tsx:65 — SystemMonitoringDashboard.SystemMonitoringDashboard has cyclomatic complexity 62 (threshold 15). Of this number, 25 points are the body's own statements and 37 belong to 14 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.
D1 · Cyclomatic Complexity · mcp_manager.handle_call (cyclomatic 58) · ×1
  • mcp_manager.handle_call (cyclomatic 58) apps/agent_web/src/mcp_manager.erl:249 — mcp_manager.handle_call has cyclomatic complexity 58 (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.
D1 · Cyclomatic Complexity · CrashMonitorDashboard.CrashMonitorDashboard (cyclomatic 58) · ×1
  • CrashMonitorDashboard.CrashMonitorDashboard (cyclomatic 58) apps/agent_web/frontend/src/components/CrashMonitorDashboard.tsx:86 — CrashMonitorDashboard.CrashMonitorDashboard has cyclomatic complexity 58 (threshold 15). Most of this is not in the body itself: 15 of the 58 points are its own statements and the rest belongs to 17 function items inside it that branch (a function literal at line 275, handleWebSocketMessage, getStatusIcon, …). 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.
D1 · Cyclomatic Complexity · ComprehensiveMCPManager.ComprehensiveMCPManager (cyclomatic 55) · ×1
  • ComprehensiveMCPManager.ComprehensiveMCPManager (cyclomatic 55) apps/agent_web/frontend/src/components/ComprehensiveMCPManager.tsx:48 — ComprehensiveMCPManager.ComprehensiveMCPManager has cyclomatic complexity 55 (threshold 15). Most of this is not in the body itself: 11 of the 55 points are its own statements and the rest belongs to 16 function items inside it that branch (testConnection, getStatusIcon, getStatusColor, …). 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.
D1 · Cyclomatic Complexity · mcp_api_handler.handle_request (cyclomatic 50) · ×1
  • mcp_api_handler.handle_request (cyclomatic 50) apps/agent_web/src/mcp_api_handler.erl:22 — mcp_api_handler.handle_request has cyclomatic complexity 50 (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.
D1 · Cyclomatic Complexity · ModelTypeEditor.ModelTypeEditor (cyclomatic 45) · ×1
  • ModelTypeEditor.ModelTypeEditor (cyclomatic 45) apps/agent_web/frontend/src/components/ModelTypeEditor.tsx:82 — ModelTypeEditor.ModelTypeEditor has cyclomatic complexity 45 (threshold 15). Most of this is not in the body itself: 4 of the 45 points are its own statements and the rest belongs to 14 function items inside it that branch (getFieldTypeIcon, saveModel, a function literal at line 374, …). 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.
D1 · Cyclomatic Complexity · ChainOfThoughtVisualization.ChainOfThoughtVisualization (cyclomatic 43) · ×1
  • ChainOfThoughtVisualization.ChainOfThoughtVisualization (cyclomatic 43) apps/agent_web/frontend/src/components/ChainOfThoughtVisualization.tsx:52 — ChainOfThoughtVisualization.ChainOfThoughtVisualization has cyclomatic complexity 43 (threshold 15). Most of this is not in the body itself: 14 of the 43 points are its own statements and the rest belongs to 12 function items inside it that branch (getStepIcon, a function literal at line 136, a function literal at line 125, …). 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.
D1 · Cyclomatic Complexity · ErrorInterpretationPanel.ErrorInterpretationPanel (cyclomatic 42) · ×1
  • ErrorInterpretationPanel.ErrorInterpretationPanel (cyclomatic 42) apps/agent_web/frontend/src/components/ErrorInterpretationPanel.tsx:55 — ErrorInterpretationPanel.ErrorInterpretationPanel has cyclomatic complexity 42 (threshold 15). Of this number, 18 points are the body's own statements and 24 belong to 11 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.
D1 · Cyclomatic Complexity · DiscoveryMeshDashboard.DiscoveryMeshDashboard (cyclomatic 42) · ×1
  • DiscoveryMeshDashboard.DiscoveryMeshDashboard (cyclomatic 42) apps/agent_web/frontend/src/components/DiscoveryMeshDashboard.tsx:55 — DiscoveryMeshDashboard.DiscoveryMeshDashboard has cyclomatic complexity 42 (threshold 15). Of this number, 18 points are the body's own statements and 24 belong to 13 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.
D1 · Cyclomatic Complexity · FleetManagementDashboard.FleetManagementDashboard (cyclomatic 41) · ×1
  • FleetManagementDashboard.FleetManagementDashboard (cyclomatic 41) apps/agent_web/frontend/src/components/FleetManagementDashboard.tsx:53 — FleetManagementDashboard.FleetManagementDashboard has cyclomatic complexity 41 (threshold 15). Most of this is not in the body itself: 11 of the 41 points are its own statements and the rest belongs to 10 function items inside it that branch (executeAutonomousOperations, a function literal at line 439, enableAutonomousMode, …). 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.
D1 · Cyclomatic Complexity · ToolRegistry.ToolRegistry (cyclomatic 41) · ×1
  • ToolRegistry.ToolRegistry (cyclomatic 41) apps/agent_web/frontend/src/components/ToolRegistry.tsx:69 — ToolRegistry.ToolRegistry has cyclomatic complexity 41 (threshold 15). Most of this is not in the body itself: 2 of the 41 points are its own statements and the rest belongs to 12 function items inside it that branch (a function literal at line 258, toggleToolInstallation, getToolIcon, …). 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.
D1 · Cyclomatic Complexity · agent_scheduling_handler.handle_request (cyclomatic 40) · ×1
  • agent_scheduling_handler.handle_request (cyclomatic 40) apps/agent_web/src/agent_scheduling_handler.erl:41 — agent_scheduling_handler.handle_request has cyclomatic complexity 40 (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.
D1 · Cyclomatic Complexity · MCPOrchestrationEngine.MCPOrchestrationEngine (cyclomatic 40) · ×1
  • MCPOrchestrationEngine.MCPOrchestrationEngine (cyclomatic 40) apps/agent_web/frontend/src/components/MCPOrchestrationEngine.tsx:165 — MCPOrchestrationEngine.MCPOrchestrationEngine has cyclomatic complexity 40 (threshold 15). Most of this is not in the body itself: 12 of the 40 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 404, loadServersAndWorkflows, a function literal at line 324, …). 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.
D1 · Cyclomatic Complexity · swarm_intelligence_engine.handle_call (cyclomatic 38) · ×1
  • swarm_intelligence_engine.handle_call (cyclomatic 38) apps/agents/src/swarm_intelligence_engine.erl:131 — swarm_intelligence_engine.handle_call has cyclomatic complexity 38 (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.
D1 · Cyclomatic Complexity · ApiKeyManager.ApiKeyManager (cyclomatic 37) · ×1
  • ApiKeyManager.ApiKeyManager (cyclomatic 37) apps/agent_web/frontend/src/components/ApiKeyManager.tsx:55 — ApiKeyManager.ApiKeyManager has cyclomatic complexity 37 (threshold 15). Most of this is not in the body itself: 15 of the 37 points are its own statements and the rest belongs to 8 function items inside it that branch (loadApiKeyStatus, loadServiceKeys, handleSaveKeys, …). 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.
D1 · Cyclomatic Complexity · mcp_orchestration_handler.handle_request (cyclomatic 36) · ×1
  • mcp_orchestration_handler.handle_request (cyclomatic 36) apps/agent_web/src/mcp_orchestration_handler.erl:15 — mcp_orchestration_handler.handle_request has cyclomatic complexity 36 (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.
D1 · Cyclomatic Complexity · PipedreamConnectionManager.PipedreamConnectionManager (cyclomatic 35) · ×1
  • PipedreamConnectionManager.PipedreamConnectionManager (cyclomatic 35) apps/agent_web/frontend/src/components/PipedreamConnectionManager.tsx:60 — PipedreamConnectionManager.PipedreamConnectionManager has cyclomatic complexity 35 (threshold 15). Most of this is not in the body itself: 5 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 305, loadApps, loadUserConnections, …). 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.
D1 · Cyclomatic Complexity · mcp_http_routes.validate_config_field (cyclomatic 34) · ×1
  • mcp_http_routes.validate_config_field (cyclomatic 34) apps/agent_web/src/mcp_http_routes.erl:198 — mcp_http_routes.validate_config_field has cyclomatic complexity 34 (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.
D1 · Cyclomatic Complexity · model_definition_manager.handle_call (cyclomatic 34) · ×1
  • model_definition_manager.handle_call (cyclomatic 34) apps/agent_web/src/model_definition_manager.erl:75 — model_definition_manager.handle_call has cyclomatic complexity 34 (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.
D1 · Cyclomatic Complexity · AdvancedStructuredOutputsManager.AdvancedStructuredOutputsManager (cyclomatic 34) · ×1
  • AdvancedStructuredOutputsManager.AdvancedStructuredOutputsManager (cyclomatic 34) apps/agent_web/frontend/src/components/AdvancedStructuredOutputsManager.tsx:62 — AdvancedStructuredOutputsManager.AdvancedStructuredOutputsManager has cyclomatic complexity 34 (threshold 15). Most of this is not in the body itself: 11 of the 34 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 75, a function literal at line 133, getCategoryIcon, …). 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.
D1 · Cyclomatic Complexity · AgentCommunicationPanel.AgentCommunicationPanel (cyclomatic 34) · ×1
  • AgentCommunicationPanel.AgentCommunicationPanel (cyclomatic 34) apps/agent_web/frontend/src/components/AgentCommunicationPanel.tsx:30 — AgentCommunicationPanel.AgentCommunicationPanel has cyclomatic complexity 34 (threshold 15). Most of this is not in the body itself: 4 of the 34 points are its own statements and the rest belongs to 10 function items inside it that branch (sendAgentMessage, a function literal at line 96, a function literal at line 200, …). 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.
D1 · Cyclomatic Complexity · DynamicUIManager.DynamicUIManager (cyclomatic 33) · ×1
  • DynamicUIManager.DynamicUIManager (cyclomatic 33) apps/agent_web/frontend/src/components/DynamicUIManager.tsx:60 — DynamicUIManager.DynamicUIManager has cyclomatic complexity 33 (threshold 15). Most of this is not in the body itself: 6 of the 33 points are its own statements and the rest belongs to 11 function items inside it that branch (a function literal at line 233, determineOptimalLayout, a function literal at line 181, …). 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.
D1 · Cyclomatic Complexity · MCPServerManager.MCPServerManager (cyclomatic 33) · ×1
  • MCPServerManager.MCPServerManager (cyclomatic 33) apps/agent_web/frontend/src/components/MCPServerManager.tsx:23 — MCPServerManager.MCPServerManager has cyclomatic complexity 33 (threshold 15). Most of this is not in the body itself: 12 of the 33 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 221, handleToggleServer, getAuthIcon, …). 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.
D1 · Cyclomatic Complexity · mcp_connection_manager.handle_call (cyclomatic 32) · ×1
  • mcp_connection_manager.handle_call (cyclomatic 32) apps/agent_web/src/mcp_connection_manager.erl:91 — mcp_connection_manager.handle_call has cyclomatic complexity 32 (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.
D1 · Cyclomatic Complexity · ModelConfiguration.ModelConfiguration (cyclomatic 31) · ×1
  • ModelConfiguration.ModelConfiguration (cyclomatic 31) apps/agent_web/frontend/src/components/ModelConfiguration.tsx:65 — ModelConfiguration.ModelConfiguration has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 6 of the 31 points are its own statements and the rest belongs to 13 function items inside it that branch (loadConfiguration, a function literal at line 422, saveModelConfig, …). 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.
D1 · Cyclomatic Complexity · ClaudeCLI.ClaudeCLI (cyclomatic 31) · ×1
  • ClaudeCLI.ClaudeCLI (cyclomatic 31) apps/agent_web/frontend/src/components/ClaudeCLI.tsx:31 — ClaudeCLI.ClaudeCLI has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 4 of the 31 points are its own statements and the rest belongs to 8 function items inside it that branch (handleKeyDown, handleCommandSubmit, a function literal at line 125, …). 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.
D1 · Cyclomatic Complexity · MCPOAuthManager.MCPOAuthManager (cyclomatic 31) · ×1
  • MCPOAuthManager.MCPOAuthManager (cyclomatic 31) apps/agent_web/frontend/src/components/MCPOAuthManager.tsx:30 — MCPOAuthManager.MCPOAuthManager has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 10 of the 31 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 51, startOAuthFlow, refreshToken, …). 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.
D1 · Cyclomatic Complexity · OAuthManager.OAuthManager (cyclomatic 31) · ×1
  • OAuthManager.OAuthManager (cyclomatic 31) apps/agent_web/frontend/src/components/OAuthManager.tsx:92 — OAuthManager.OAuthManager has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 2 of the 31 points are its own statements and the rest belongs to 13 function items inside it that branch (initiateOAuth, setupMessageListener::handleMessage, revokeAuth, …). 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.
D1 · Cyclomatic Complexity · QuantumConsciousnessInterface.QuantumConsciousnessInterface (cyclomatic 31) · ×1
  • QuantumConsciousnessInterface.QuantumConsciousnessInterface (cyclomatic 31) apps/agent_web/frontend/src/components/QuantumConsciousnessInterface.tsx:59 — QuantumConsciousnessInterface.QuantumConsciousnessInterface has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 6 of the 31 points are its own statements and the rest belongs to 11 function items inside it that branch (drawQuantumConsciousnessField, a function literal at line 413, a function literal at line 102, …). 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.
D1 · Cyclomatic Complexity · InteractiveReasoningControls.InteractiveReasoningControls (cyclomatic 30) · ×1
  • InteractiveReasoningControls.InteractiveReasoningControls (cyclomatic 30) apps/agent_web/frontend/src/components/InteractiveReasoningControls.tsx:53 — InteractiveReasoningControls.InteractiveReasoningControls has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 13 of the 30 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 112, 158, 193, …). 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.
D1 · Cyclomatic Complexity · MultiAgentChat.MultiAgentChat (cyclomatic 30) · ×1
  • MultiAgentChat.MultiAgentChat (cyclomatic 30) apps/agent_web/frontend/src/components/MultiAgentChat.tsx:39 — MultiAgentChat.MultiAgentChat has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 14 of the 30 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 54, createGroupChat, createSingleAgentSession, …). 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.
D1 · Cyclomatic Complexity · agent_tools.handle_call (cyclomatic 29) · ×1
  • agent_tools.handle_call (cyclomatic 29) apps/agents/src/agent_tools.erl:134 — agent_tools.handle_call has cyclomatic complexity 29 (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.
D1 · Cyclomatic Complexity · consciousness_simulation_engine.handle_call (cyclomatic 29) · ×1
  • consciousness_simulation_engine.handle_call (cyclomatic 29) apps/agents/src/consciousness_simulation_engine.erl:162 — consciousness_simulation_engine.handle_call has cyclomatic complexity 29 (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.
D1 · Cyclomatic Complexity · agent_api_handler.create_agent_by_type (cyclomatic 28) · ×1
  • agent_api_handler.create_agent_by_type (cyclomatic 28) apps/agent_web/src/agent_api_handler.erl:288 — agent_api_handler.create_agent_by_type has cyclomatic complexity 28 (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.
D1 · Cyclomatic Complexity · dimensional_phase_shift_engine.handle_call (cyclomatic 28) · ×1
  • dimensional_phase_shift_engine.handle_call (cyclomatic 28) apps/agents/src/dimensional_phase_shift_engine.erl:174 — dimensional_phase_shift_engine.handle_call has cyclomatic complexity 28 (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.
D1 · Cyclomatic Complexity · temporal_transcendence_engine.handle_call (cyclomatic 28) · ×1
  • temporal_transcendence_engine.handle_call (cyclomatic 28) apps/agents/src/temporal_transcendence_engine.erl:163 — temporal_transcendence_engine.handle_call has cyclomatic complexity 28 (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.
D1 · Cyclomatic Complexity · DenseApp.DenseApp (cyclomatic 28) · ×1
  • DenseApp.DenseApp (cyclomatic 28) REDACTED:34 — DenseApp.DenseApp has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 4 of the 28 points are its own statements and the rest belongs to 7 function items inside it that branch (renderPanel, handleWebSocketMessage, createAgent, …). 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.
D1 · Cyclomatic Complexity · examples_handler.run_example (cyclomatic 27) · ×1
  • examples_handler.run_example (cyclomatic 27) apps/agent_web/src/examples_handler.erl:69 — examples_handler.run_example has cyclomatic complexity 27 (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.
D1 · Cyclomatic Complexity · agent_tool_registry.handle_call (cyclomatic 27) · ×1
  • agent_tool_registry.handle_call (cyclomatic 27) apps/agents/src/agent_tool_registry.erl:96 — agent_tool_registry.handle_call has cyclomatic complexity 27 (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.
D1 · Cyclomatic Complexity · AgentQuorumPanel.AgentQuorumPanel (cyclomatic 27) · ×1
  • AgentQuorumPanel.AgentQuorumPanel (cyclomatic 27) apps/agent_web/frontend/src/components/AgentQuorumPanel.tsx:36 — AgentQuorumPanel.AgentQuorumPanel has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 2 of the 27 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 279, a function literal at line 225, proposeDecision, …). 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.
D1 · Cyclomatic Complexity · knowledge_base_handler.handle_request (cyclomatic 26) · ×1
  • knowledge_base_handler.handle_request (cyclomatic 26) apps/agent_web/src/knowledge_base_handler.erl:11 — knowledge_base_handler.handle_request has cyclomatic complexity 26 (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.
D1 · Cyclomatic Complexity · agent_collaboration.handle_call (cyclomatic 26) · ×1
  • agent_collaboration.handle_call (cyclomatic 26) apps/agents/src/agent_collaboration.erl:83 — agent_collaboration.handle_call has cyclomatic complexity 26 (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.
D1 · Cyclomatic Complexity · agent_dynamic_system.handle_call (cyclomatic 26) · ×1
  • agent_dynamic_system.handle_call (cyclomatic 26) apps/agents/src/agent_dynamic_system.erl:104 — agent_dynamic_system.handle_call has cyclomatic complexity 26 (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.
D1 · Cyclomatic Complexity · agent_ws_handler.websocket_handle (cyclomatic 25) · ×1
  • agent_ws_handler.websocket_handle (cyclomatic 25) apps/agent_web/src/agent_ws_handler.erl:22 — agent_ws_handler.websocket_handle has cyclomatic complexity 25 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · oauth_manager.handle_call (cyclomatic 25) · ×1
  • oauth_manager.handle_call (cyclomatic 25) apps/agent_web/src/oauth_manager.erl:94 — oauth_manager.handle_call has cyclomatic complexity 25 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · self_modifying_agent_engine.handle_call (cyclomatic 25) · ×1
  • self_modifying_agent_engine.handle_call (cyclomatic 25) apps/agents/src/self_modifying_agent_engine.erl:105 — self_modifying_agent_engine.handle_call has cyclomatic complexity 25 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · openai_chat.do_create_chat_completion (cyclomatic 25) · ×1
  • openai_chat.do_create_chat_completion (cyclomatic 25) apps/openai/src/openai_chat.erl:143 — openai_chat.do_create_chat_completion has cyclomatic complexity 25 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · SimpleAdvancedChat.AdvancedMessageContent (cyclomatic 25) · ×1
  • SimpleAdvancedChat.AdvancedMessageContent (cyclomatic 25) REDACTED:77 — SimpleAdvancedChat.AdvancedMessageContent has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 7 of the 25 points are its own statements and the rest belongs to 4 function items inside it that branch (renderMarkdown, renderJSON, renderHTML, …). 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.
D1 · Cyclomatic Complexity · agent_discovery.handle_call (cyclomatic 24) · ×1
  • agent_discovery.handle_call (cyclomatic 24) apps/agents/src/agent_discovery.erl:133 — agent_discovery.handle_call has cyclomatic complexity 24 (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.
D1 · Cyclomatic Complexity · token_stream_fsm.streaming (cyclomatic 24) · ×1
  • token_stream_fsm.streaming (cyclomatic 24) apps/openai/src/token_stream_fsm.erl:244 — token_stream_fsm.streaming has cyclomatic complexity 24 (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.
D1 · Cyclomatic Complexity · openapi_validator.validate_parameter (cyclomatic 24) · ×1
  • openapi_validator.validate_parameter (cyclomatic 24) apps/openapi_scaffold/src/openapi_validator.erl:121 — openapi_validator.validate_parameter has cyclomatic complexity 24 (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.
D1 · Cyclomatic Complexity · AdaptiveAIInterface.AdaptiveAIInterface (cyclomatic 24) · ×1
  • AdaptiveAIInterface.AdaptiveAIInterface (cyclomatic 24) apps/agent_web/frontend/src/components/AdaptiveAIInterface.tsx:46 — AdaptiveAIInterface.AdaptiveAIInterface has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 6 of the 24 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 131, 212, 205, …). 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.
D1 · Cyclomatic Complexity · pipedream_auth_handler.handle_call (cyclomatic 23) · ×1
  • pipedream_auth_handler.handle_call (cyclomatic 23) apps/agent_web/src/pipedream_auth_handler.erl:68 — pipedream_auth_handler.handle_call has cyclomatic complexity 23 (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.
D1 · Cyclomatic Complexity · dynamic_supervisor_manager.handle_call (cyclomatic 23) · ×1
  • dynamic_supervisor_manager.handle_call (cyclomatic 23) apps/agents/src/dynamic_supervisor_manager.erl:78 — dynamic_supervisor_manager.handle_call has cyclomatic complexity 23 (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.
D1 · Cyclomatic Complexity · mcp_oauth_handler.handle_request (cyclomatic 22) · ×1
  • mcp_oauth_handler.handle_request (cyclomatic 22) apps/agent_web/src/mcp_oauth_handler.erl:21 — mcp_oauth_handler.handle_request has cyclomatic complexity 22 (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.
D1 · Cyclomatic Complexity · openapi_dynamic_handler.generate_mock_for_type (cyclomatic 22) · ×1
  • openapi_dynamic_handler.generate_mock_for_type (cyclomatic 22) apps/openapi_scaffold/src/openapi_dynamic_handler.erl:158 — openapi_dynamic_handler.generate_mock_for_type has cyclomatic complexity 22 (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.
D1 · Cyclomatic Complexity · Dashboard.Dashboard (cyclomatic 22) · ×1
  • Dashboard.Dashboard (cyclomatic 22) REDACTED:47 — Dashboard.Dashboard has cyclomatic complexity 22 (threshold 15). Of this number, 18 points are the body's own statements and 4 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.
D1 · Cyclomatic Complexity · MultiAgentChat.GroupChatInterface (cyclomatic 22) · ×1
  • MultiAgentChat.GroupChatInterface (cyclomatic 22) apps/agent_web/frontend/src/components/MultiAgentChat.tsx:351 — MultiAgentChat.GroupChatInterface has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 2 of the 22 points are its own statements and the rest belongs to 6 function items inside it that branch (sendToGroup, a function literal at line 392, a function literal at line 484, …). 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.
D1 · Cyclomatic Complexity · crash_report_api_handler.handle_get_path (cyclomatic 21) · ×1
  • crash_report_api_handler.handle_get_path (cyclomatic 21) apps/agent_web/src/crash_report_api_handler.erl:32 — crash_report_api_handler.handle_get_path has cyclomatic complexity 21 (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.
D1 · Cyclomatic Complexity · mcp_oauth_client.handle_call (cyclomatic 21) · ×1
  • mcp_oauth_client.handle_call (cyclomatic 21) apps/agent_web/src/mcp_oauth_client.erl:60 — mcp_oauth_client.handle_call has cyclomatic complexity 21 (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.
D1 · Cyclomatic Complexity · streaming_function_handler.process_token_for_display (cyclomatic 21) · ×1
  • streaming_function_handler.process_token_for_display (cyclomatic 21) apps/agents/src/streaming_function_handler.erl:458 — streaming_function_handler.process_token_for_display has cyclomatic complexity 21 (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.
D1 · Cyclomatic Complexity · mcp_server.handle_mcp_request (cyclomatic 20) · ×1
  • mcp_server.handle_mcp_request (cyclomatic 20) apps/agent_web/src/mcp_server.erl:647 — mcp_server.handle_mcp_request has cyclomatic complexity 20 (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.
D1 · Cyclomatic Complexity · agent_tools.execute_file_list (cyclomatic 20) · ×1
  • agent_tools.execute_file_list (cyclomatic 20) apps/agents/src/agent_tools.erl:3106 — agent_tools.execute_file_list has cyclomatic complexity 20 (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.
D1 · Cyclomatic Complexity · SimpleAdvancedChat.ContentAnalysisBadge (cyclomatic 20) · ×1
  • SimpleAdvancedChat.ContentAnalysisBadge (cyclomatic 20) REDACTED:323 — SimpleAdvancedChat.ContentAnalysisBadge has cyclomatic complexity 20 (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.
D1 · Cyclomatic Complexity · CommandPalette.CommandPalette (cyclomatic 20) · ×1
  • CommandPalette.CommandPalette (cyclomatic 20) apps/agent_web/frontend/src/components/CommandPalette.tsx:28 — CommandPalette.CommandPalette has cyclomatic complexity 20 (threshold 15). Of this number, 10 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.
D1 · Cyclomatic Complexity · consciousness_bridge_api_handler.handle_post (cyclomatic 19) · ×1
  • consciousness_bridge_api_handler.handle_post (cyclomatic 19) apps/agent_web/src/consciousness_bridge_api_handler.erl:103 — consciousness_bridge_api_handler.handle_post has cyclomatic complexity 19 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · mcp_client_v2.start_websocket_connection (cyclomatic 19) · ×1
  • mcp_client_v2.start_websocket_connection (cyclomatic 19) apps/agent_web/src/mcp_client_v2.erl:300 — mcp_client_v2.start_websocket_connection has cyclomatic complexity 19 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · mcp_server_config.add_server (cyclomatic 19) · ×1
  • mcp_server_config.add_server (cyclomatic 19) apps/agents/src/mcp_server_config.erl:473 — mcp_server_config.add_server has cyclomatic complexity 19 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · openapi_introspection.handle_call (cyclomatic 19) · ×1
  • openapi_introspection.handle_call (cyclomatic 19) apps/openapi_scaffold/src/openapi_introspection.erl:49 — openapi_introspection.handle_call has cyclomatic complexity 19 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · DenseDashboard.DenseDashboard (cyclomatic 19) · ×1
  • DenseDashboard.DenseDashboard (cyclomatic 19) apps/agent_web/frontend/src/components/DenseDashboard.tsx:15 — DenseDashboard.DenseDashboard has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 5 of the 19 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 85, 36, 16, …). 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.
D1 · Cyclomatic Complexity · mcp_client_v2.handle_call (cyclomatic 18) · ×1
  • mcp_client_v2.handle_call (cyclomatic 18) apps/agent_web/src/mcp_client_v2.erl:105 — mcp_client_v2.handle_call has cyclomatic complexity 18 (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.
D1 · Cyclomatic Complexity · mcp_client_v2.send_message (cyclomatic 18) · ×1
  • mcp_client_v2.send_message (cyclomatic 18) apps/agent_web/src/mcp_client_v2.erl:733 — mcp_client_v2.send_message has cyclomatic complexity 18 (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.
D1 · Cyclomatic Complexity · mcp_http_session_manager.handle_call (cyclomatic 18) · ×1
  • mcp_http_session_manager.handle_call (cyclomatic 18) apps/agent_web/src/mcp_http_session_manager.erl:158 — mcp_http_session_manager.handle_call has cyclomatic complexity 18 (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.
D1 · Cyclomatic Complexity · specialized_agent_factory.handle_call (cyclomatic 18) · ×1
  • specialized_agent_factory.handle_call (cyclomatic 18) apps/agents/src/specialized_agent_factory.erl:82 — specialized_agent_factory.handle_call has cyclomatic complexity 18 (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.
D1 · Cyclomatic Complexity · openai_chat.do_create_streaming_completion (cyclomatic 18) · ×1
  • openai_chat.do_create_streaming_completion (cyclomatic 18) apps/openai/src/openai_chat.erl:277 — openai_chat.do_create_streaming_completion has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing. This is NOT this file's highest cyclomatic complexity: openai_chat.process_streaming_event (cyclomatic 25) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.
D1 · Cyclomatic Complexity · ResourceSentinelBar.ResourceSentinelBar (cyclomatic 18) · ×1
  • ResourceSentinelBar.ResourceSentinelBar (cyclomatic 18) apps/agent_web/frontend/src/components/ResourceSentinelBar.tsx:30 — ResourceSentinelBar.ResourceSentinelBar has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 2 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 38, getThresholdColor, getTrendIcon). 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.
D1 · Cyclomatic Complexity · AdvancedMessageRenderer.AdvancedMessageRenderer · ×1
  • AdvancedMessageRenderer.AdvancedMessageRenderer::analyzeContent (cyclomatic 18) apps/agent_web/frontend/src/components/AdvancedMessageRenderer.tsx:43 — AdvancedMessageRenderer.AdvancedMessageRenderer::analyzeContent 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.
D1 · Cyclomatic Complexity · conversation_stats_logger.handle_cast (cyclomatic 17) · ×1
  • conversation_stats_logger.handle_cast (cyclomatic 17) apps/agent_web/src/conversation_stats_logger.erl:80 — conversation_stats_logger.handle_cast has cyclomatic complexity 17 (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.
D1 · Cyclomatic Complexity · mcp_registry.handle_call (cyclomatic 17) · ×1
  • mcp_registry.handle_call (cyclomatic 17) apps/agent_web/src/mcp_registry.erl:66 — mcp_registry.handle_call has cyclomatic complexity 17 (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.
D1 · Cyclomatic Complexity · neural_swarm_api_handler.handle_post (cyclomatic 17) · ×1
  • neural_swarm_api_handler.handle_post (cyclomatic 17) apps/agent_web/src/neural_swarm_api_handler.erl:89 — neural_swarm_api_handler.handle_post has cyclomatic complexity 17 (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.
D1 · Cyclomatic Complexity · mcp_advanced_config.handle_call (cyclomatic 16) · ×1
  • mcp_advanced_config.handle_call (cyclomatic 16) apps/agent_web/src/mcp_advanced_config.erl:57 — mcp_advanced_config.handle_call has cyclomatic complexity 16 (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.
D1 · Cyclomatic Complexity · SeedServersDialog.SeedServersDialog (cyclomatic 16) · ×1
  • SeedServersDialog.SeedServersDialog (cyclomatic 16) apps/agent_web/frontend/src/components/SeedServersDialog.tsx:116 — SeedServersDialog.SeedServersDialog has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 4 function items inside it that branch (addServer, a function literal at line 212, getAuthIcon, …). 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.
D1 · Cyclomatic Complexity · AdvancedMCPDashboard.ServerDetailPanel (cyclomatic 16) · ×1
  • AdvancedMCPDashboard.ServerDetailPanel (cyclomatic 16) REDACTED:1222 — AdvancedMCPDashboard.ServerDetailPanel has cyclomatic complexity 16 (threshold 15). Of this number, 12 points are the body's own statements and 4 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.
D12 · Dependency Hygiene · Floating source dependency · ×1
  • Floating source dependency: jesse — Runtime dependency `jesse` is fetched from source in rebar.config and tracks branch `master` — the declaration pins no immutable revision, so `rebar3 upgrade` moves this dependency to code nobody reviewed. Pin it with `{tag, "v1.2.3"}` or `{ref, "<full commit SHA>"}`.
D12 · Dependency Hygiene · Dependency not covered by the lockfile · ×1
  • Dependency not covered by the lockfile: jsx — `jsx` is declared in sandbox/myapp/rebar.config but has no entry in the committed `REDACTED`, so its version is resolved rather than pinned. Run `rebar3 compile` and commit the updated lockfile.
D2 · Cognitive Complexity · SimpleAdvancedChat.SimpleAdvancedChat (cognitive 100) · ×1
  • SimpleAdvancedChat.SimpleAdvancedChat (cognitive 100) REDACTED:384 — SimpleAdvancedChat.SimpleAdvancedChat has cognitive complexity 100 (threshold 15). Drivers by points: if/else 37 (46 pts), boolean chains 35, error handling 9, ternaries 8, loops 1, match/switch 1 (nesting depth added 9). Most of this is not in the body itself: 13 of the 100 points are its own statements and the rest belongs to 24 function items inside it that branch (sendMessage, a function literal at line 527, detectMessageType, …). 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.
D2 · Cognitive Complexity · colored_io.detect_log_type (cognitive 90) · ×1
  • colored_io.detect_log_type (cognitive 90) apps/agent_web/src/colored_io.erl:54 — colored_io.detect_log_type has cognitive complexity 90 (threshold 15). Drivers by points: match/switch 24 (90 pts) (nesting depth added 66). 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.
D2 · Cognitive Complexity · AdvancedMCPDashboard.AdvancedMCPDashboard (cognitive 89) · ×1
  • AdvancedMCPDashboard.AdvancedMCPDashboard (cognitive 89) REDACTED:157 — AdvancedMCPDashboard.AdvancedMCPDashboard has cognitive complexity 89 (threshold 15). Drivers by points: boolean chains 33, if/else 20, ternaries 15 (17 pts), match/switch 8 (9 pts), error handling 7, loops 2 (3 pts) (nesting depth added 4). Most of this is not in the body itself: 6 of the 89 points are its own statements and the rest belongs to 35 function items inside it that branch (ServerDetails, connectServer, disconnectServer, …). 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.
D2 · Cognitive Complexity · AdvancedMessageRenderer.AdvancedMessageRenderer (cognitive 62) · ×1
  • AdvancedMessageRenderer.AdvancedMessageRenderer (cognitive 62) apps/agent_web/frontend/src/components/AdvancedMessageRenderer.tsx:22 — AdvancedMessageRenderer.AdvancedMessageRenderer has cognitive complexity 62 (threshold 15). Drivers by points: if/else 23 (31 pts), boolean chains 23, loops 5, ternaries 3 (nesting depth added 8). Most of this is not in the body itself: 8 of the 62 points are its own statements and the rest belongs to 10 function items inside it that branch (analyzeContent, parseInlineMath, parseAdvancedContent, …). 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.
D2 · Cognitive Complexity · CrashMonitorDashboard.CrashMonitorDashboard (cognitive 56) · ×1
  • CrashMonitorDashboard.CrashMonitorDashboard (cognitive 56) apps/agent_web/frontend/src/components/CrashMonitorDashboard.tsx:86 — CrashMonitorDashboard.CrashMonitorDashboard has cognitive complexity 56 (threshold 15). Drivers by points: ternaries 9 (19 pts), boolean chains 16, if/else 10 (12 pts), error handling 6, match/switch 3 (nesting depth added 12). Of this number, 16 points are the body's own statements and 40 belong to 17 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · agent_tools.execute_file_list (cognitive 50) · ×1
  • agent_tools.execute_file_list (cognitive 50) apps/agents/src/agent_tools.erl:3106 — agent_tools.execute_file_list has cognitive complexity 50 (threshold 15). Drivers by points: match/switch 12 (31 pts), if/else 2 (10 pts), loops 2 (8 pts), error handling 1 (nesting depth added 33). 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.
D2 · Cognitive Complexity · ModelTypeEditor.ModelTypeEditor (cognitive 50) · ×1
  • ModelTypeEditor.ModelTypeEditor (cognitive 50) apps/agent_web/frontend/src/components/ModelTypeEditor.tsx:82 — ModelTypeEditor.ModelTypeEditor has cognitive complexity 50 (threshold 15). Drivers by points: ternaries 13 (27 pts), if/else 9 (10 pts), boolean chains 9, error handling 2, match/switch 2 (nesting depth added 15). Most of this is not in the body itself: 5 of the 50 points are its own statements and the rest belongs to 14 function items inside it that branch (a function literal at line 374, saveModel, loadModels, …). 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.
D2 · Cognitive Complexity · ComprehensiveMCPManager.ComprehensiveMCPManager (cognitive 49) · ×1
  • ComprehensiveMCPManager.ComprehensiveMCPManager (cognitive 49) apps/agent_web/frontend/src/components/ComprehensiveMCPManager.tsx:48 — ComprehensiveMCPManager.ComprehensiveMCPManager has cognitive complexity 49 (threshold 15). Drivers by points: if/else 18 (21 pts), boolean chains 13, error handling 11, match/switch 2, ternaries 2 (nesting depth added 3). Most of this is not in the body itself: 7 of the 49 points are its own statements and the rest belongs to 16 function items inside it that branch (testConnection, startLocalServer, stopLocalServer, …). 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.
D2 · Cognitive Complexity · SystemMonitoringDashboard.SystemMonitoringDashboard (cognitive 47) · ×1
  • SystemMonitoringDashboard.SystemMonitoringDashboard (cognitive 47) apps/agent_web/frontend/src/components/SystemMonitoringDashboard.tsx:65 — SystemMonitoringDashboard.SystemMonitoringDashboard has cognitive complexity 47 (threshold 15). Drivers by points: boolean chains 23, if/else 12, ternaries 6, error handling 4, match/switch 2. Of this number, 21 points are the body's own statements and 26 belong to 14 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.
D2 · Cognitive Complexity · Timeline.Timeline (cognitive 46) · ×1
  • Timeline.Timeline (cognitive 46) apps/agent_web/frontend/src/components/Timeline.tsx:59 — Timeline.Timeline has cognitive complexity 46 (threshold 15). Drivers by points: boolean chains 20, if/else 14, error handling 4 (6 pts), match/switch 4, ternaries 2 (nesting depth added 2). Most of this is not in the body itself: 3 of the 46 points are its own statements and the rest belongs to 15 function items inside it that branch (a function literal at line 492, handleWebSocketEvent, a function literal at line 263, …). 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.
D2 · Cognitive Complexity · App.App (cognitive 45) · ×1
  • App.App (cognitive 45) apps/agent_web/frontend/src/App.tsx:55 — App.App has cognitive complexity 45 (threshold 15). Drivers by points: boolean chains 22, if/else 9 (10 pts), error handling 6 (7 pts), ternaries 4, match/switch 2 (nesting depth added 2). Most of this is not in the body itself: 4 of the 45 points are its own statements and the rest belongs to 14 function items inside it that branch (loadSystemMetrics, a function literal at line 226, handleExecuteAction, …). 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.
D2 · Cognitive Complexity · FleetManagementDashboard.FleetManagementDashboard (cognitive 43) · ×1
  • FleetManagementDashboard.FleetManagementDashboard (cognitive 43) apps/agent_web/frontend/src/components/FleetManagementDashboard.tsx:53 — FleetManagementDashboard.FleetManagementDashboard has cognitive complexity 43 (threshold 15). Drivers by points: boolean chains 17, if/else 15, error handling 5, ternaries 5, match/switch 1. Most of this is not in the body itself: 10 of the 43 points are its own statements and the rest belongs to 10 function items inside it that branch (executeAutonomousOperations, enableAutonomousMode, broadcastToFleet, …). 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.
D2 · Cognitive Complexity · embedding_integration.handle_call (cognitive 40) · ×1
  • embedding_integration.handle_call (cognitive 40) apps/agent_web/src/embedding_integration.erl:86 — embedding_integration.handle_call has cognitive complexity 40 (threshold 15). Drivers by points: match/switch 14 (33 pts), error handling 7 (nesting depth added 19). 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.
D2 · Cognitive Complexity · OAuthManager.OAuthManager (cognitive 40) · ×1
  • OAuthManager.OAuthManager (cognitive 40) apps/agent_web/frontend/src/components/OAuthManager.tsx:92 — OAuthManager.OAuthManager has cognitive complexity 40 (threshold 15). Drivers by points: if/else 21 (25 pts), boolean chains 5, error handling 5, ternaries 2 (4 pts), loops 1 (nesting depth added 6). Most of this is not in the body itself: 1 of the 40 points is its own statement and the rest belongs to 13 function items inside it that branch (initiateOAuth, revokeAuth, checkAllAuthStatuses, …). 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.
D2 · Cognitive Complexity · ToolRegistry.ToolRegistry (cognitive 38) · ×1
  • ToolRegistry.ToolRegistry (cognitive 38) apps/agent_web/frontend/src/components/ToolRegistry.tsx:69 — ToolRegistry.ToolRegistry has cognitive complexity 38 (threshold 15). Drivers by points: ternaries 10 (15 pts), boolean chains 8, if/else 8, error handling 5, match/switch 2 (nesting depth added 5). Most of this is not in the body itself: 1 of the 38 points is its own statement and the rest belongs to 12 function items inside it that branch (toggleToolInstallation, loadTools, loadMcpServers, …). 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.
D2 · Cognitive Complexity · ClaudeCLI.ClaudeCLI (cognitive 37) · ×1
  • ClaudeCLI.ClaudeCLI (cognitive 37) apps/agent_web/frontend/src/components/ClaudeCLI.tsx:31 — ClaudeCLI.ClaudeCLI has cognitive complexity 37 (threshold 15). Drivers by points: if/else 14 (17 pts), ternaries 5 (10 pts), boolean chains 8, error handling 2 (nesting depth added 8). Most of this is not in the body itself: 3 of the 37 points are its own statements and the rest belongs to 8 function items inside it that branch (handleKeyDown, a function literal at line 125, handleCommandSubmit, …). 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.
D2 · Cognitive Complexity · distributed_consensus_tracker.calculate_efficiency_metrics (cognitive 35) · ×1
  • distributed_consensus_tracker.calculate_efficiency_metrics (cognitive 35) apps/agent_web/src/distributed_consensus_tracker.erl:741 — distributed_consensus_tracker.calculate_efficiency_metrics has cognitive complexity 35 (threshold 15). Drivers by points: loops 5 (15 pts), match/switch 8 (13 pts), if/else 2 (7 pts) (nesting depth added 20). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · DiscoveryMeshDashboard.DiscoveryMeshDashboard (cognitive 35) · ×1
  • DiscoveryMeshDashboard.DiscoveryMeshDashboard (cognitive 35) apps/agent_web/frontend/src/components/DiscoveryMeshDashboard.tsx:55 — DiscoveryMeshDashboard.DiscoveryMeshDashboard has cognitive complexity 35 (threshold 15). Drivers by points: boolean chains 14, ternaries 9, error handling 5, if/else 5, match/switch 2. Of this number, 17 points are the body's own statements and 18 belong to 13 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · mcp_api_handler.handle_request (cognitive 34) · ×1
  • mcp_api_handler.handle_request (cognitive 34) apps/agent_web/src/mcp_api_handler.erl:22 — mcp_api_handler.handle_request has cognitive complexity 34 (threshold 15). Drivers by points: match/switch 25 (32 pts), boolean chains 1, error handling 1 (nesting depth added 7). 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.
D2 · Cognitive Complexity · MCPOrchestrationEngine.MCPOrchestrationEngine (cognitive 34) · ×1
  • MCPOrchestrationEngine.MCPOrchestrationEngine (cognitive 34) apps/agent_web/frontend/src/components/MCPOrchestrationEngine.tsx:165 — MCPOrchestrationEngine.MCPOrchestrationEngine has cognitive complexity 34 (threshold 15). Drivers by points: boolean chains 21, if/else 7, error handling 6. Most of this is not in the body itself: 11 of the 34 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 404, loadServersAndWorkflows, a function literal at line 324, …). 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.
D2 · Cognitive Complexity · MCPOAuthManager.MCPOAuthManager (cognitive 34) · ×1
  • MCPOAuthManager.MCPOAuthManager (cognitive 34) apps/agent_web/frontend/src/components/MCPOAuthManager.tsx:30 — MCPOAuthManager.MCPOAuthManager has cognitive complexity 34 (threshold 15). Drivers by points: if/else 12 (13 pts), ternaries 5 (9 pts), boolean chains 7, error handling 5 (nesting depth added 5). Most of this is not in the body itself: 9 of the 34 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 51, startOAuthFlow, refreshToken, …). 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.
D2 · Cognitive Complexity · PipedreamConnectionManager.PipedreamConnectionManager (cognitive 34) · ×1
  • PipedreamConnectionManager.PipedreamConnectionManager (cognitive 34) apps/agent_web/frontend/src/components/PipedreamConnectionManager.tsx:60 — PipedreamConnectionManager.PipedreamConnectionManager has cognitive complexity 34 (threshold 15). Drivers by points: boolean chains 10, error handling 8, if/else 8, ternaries 7 (8 pts) (nesting depth added 1). Most of this is not in the body itself: 4 of the 34 points are its own statements and the rest belongs to 12 function items inside it that branch (a function literal at line 305, loadApps, loadUserConnections, …). 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.
D2 · Cognitive Complexity · AgentQuorumPanel.AgentQuorumPanel (cognitive 33) · ×1
  • AgentQuorumPanel.AgentQuorumPanel (cognitive 33) apps/agent_web/frontend/src/components/AgentQuorumPanel.tsx:36 — AgentQuorumPanel.AgentQuorumPanel has cognitive complexity 33 (threshold 15). Drivers by points: ternaries 14 (22 pts), boolean chains 6, if/else 3, error handling 2 (nesting depth added 8). Most of this is not in the body itself: 1 of the 33 points is its own statement and the rest belongs to 9 function items inside it that branch (a function literal at line 279, a function literal at line 225, proposeDecision, …). 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.
D2 · Cognitive Complexity · QuantumConsciousnessInterface.QuantumConsciousnessInterface (cognitive 33) · ×1
  • QuantumConsciousnessInterface.QuantumConsciousnessInterface (cognitive 33) apps/agent_web/frontend/src/components/QuantumConsciousnessInterface.tsx:59 — QuantumConsciousnessInterface.QuantumConsciousnessInterface has cognitive complexity 33 (threshold 15). Drivers by points: if/else 12 (14 pts), ternaries 7 (8 pts), boolean chains 4, loops 4, error handling 3 (nesting depth added 3). Most of this is not in the body itself: 5 of the 33 points are its own statements and the rest belongs to 11 function items inside it that branch (drawQuantumConsciousnessField, a function literal at line 102, a function literal at line 245, …). 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.
D2 · Cognitive Complexity · agent_tools.predefined_executor (cognitive 32) · ×1
  • agent_tools.predefined_executor (cognitive 32) apps/agents/src/agent_tools.erl:1319 — agent_tools.predefined_executor has cognitive complexity 32 (threshold 15). Drivers by points: match/switch 16 (30 pts), loops 1 (2 pts) (nesting depth added 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. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · ChainOfThoughtVisualization.ChainOfThoughtVisualization (cognitive 32) · ×1
  • ChainOfThoughtVisualization.ChainOfThoughtVisualization (cognitive 32) apps/agent_web/frontend/src/components/ChainOfThoughtVisualization.tsx:52 — ChainOfThoughtVisualization.ChainOfThoughtVisualization has cognitive complexity 32 (threshold 15). Drivers by points: if/else 16 (17 pts), boolean chains 11, ternaries 2, error handling 1, match/switch 1 (nesting depth added 1). Most of this is not in the body itself: 10 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 98, a function literal at line 125, getConfidenceColor, …). 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.
D2 · Cognitive Complexity · ApiKeyManager.ApiKeyManager (cognitive 32) · ×1
  • ApiKeyManager.ApiKeyManager (cognitive 32) apps/agent_web/frontend/src/components/ApiKeyManager.tsx:55 — ApiKeyManager.ApiKeyManager has cognitive complexity 32 (threshold 15). Drivers by points: boolean chains 16, if/else 7 (8 pts), error handling 4, ternaries 4 (nesting depth added 1). Most of this is not in the body itself: 11 of the 32 points are its own statements and the rest belongs to 8 function items inside it that branch (loadApiKeyStatus, handleSaveKeys, loadServiceKeys, …). 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.
D2 · Cognitive Complexity · DynamicUIManager.DynamicUIManager (cognitive 32) · ×1
  • DynamicUIManager.DynamicUIManager (cognitive 32) apps/agent_web/frontend/src/components/DynamicUIManager.tsx:60 — DynamicUIManager.DynamicUIManager has cognitive complexity 32 (threshold 15). Drivers by points: boolean chains 21, if/else 7, ternaries 3 (4 pts) (nesting depth added 1). Most of this is not in the body itself: 5 of the 32 points are its own statements and the rest belongs to 11 function items inside it that branch (a function literal at line 233, determineOptimalLayout, a function literal at line 181, …). 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.
D2 · Cognitive Complexity · openai_chat.do_create_chat_completion (cognitive 31) · ×1
  • openai_chat.do_create_chat_completion (cognitive 31) apps/openai/src/openai_chat.erl:143 — openai_chat.do_create_chat_completion has cognitive complexity 31 (threshold 15). Drivers by points: match/switch 22 (28 pts), error handling 2 (3 pts) (nesting depth added 7). 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.
D2 · Cognitive Complexity · ErrorInterpretationPanel.ErrorInterpretationPanel (cognitive 31) · ×1
  • ErrorInterpretationPanel.ErrorInterpretationPanel (cognitive 31) apps/agent_web/frontend/src/components/ErrorInterpretationPanel.tsx:55 — ErrorInterpretationPanel.ErrorInterpretationPanel has cognitive complexity 31 (threshold 15). Drivers by points: boolean chains 15, if/else 7, ternaries 4 (5 pts), error handling 2, match/switch 2 (nesting depth added 1). Most of this is not in the body itself: 14 of the 31 points are its own statements and the rest belongs to 11 function items inside it that branch (a function literal at line 109, interpretCustomError, fetchInterpretations, …). 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.
D2 · Cognitive Complexity · AgentCommunicationPanel.AgentCommunicationPanel (cognitive 31) · ×1
  • AgentCommunicationPanel.AgentCommunicationPanel (cognitive 31) apps/agent_web/frontend/src/components/AgentCommunicationPanel.tsx:30 — AgentCommunicationPanel.AgentCommunicationPanel has cognitive complexity 31 (threshold 15). Drivers by points: boolean chains 15, ternaries 5 (8 pts), if/else 7, error handling 1 (nesting depth added 3). Most of this is not in the body itself: 2 of the 31 points are its own statements and the rest belongs to 10 function items inside it that branch (sendAgentMessage, a function literal at line 96, a function literal at line 200, …). 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.
D2 · Cognitive Complexity · ModelConfiguration.ModelConfiguration (cognitive 30) · ×1
  • ModelConfiguration.ModelConfiguration (cognitive 30) apps/agent_web/frontend/src/components/ModelConfiguration.tsx:65 — ModelConfiguration.ModelConfiguration has cognitive complexity 30 (threshold 15). Drivers by points: ternaries 8 (9 pts), if/else 8, boolean chains 7, error handling 6 (nesting depth added 1). Most of this is not in the body itself: 5 of the 30 points are its own statements and the rest belongs to 13 function items inside it that branch (loadConfiguration, a function literal at line 422, saveModelConfig, …). 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.
D2 · Cognitive Complexity · MCPServerManager.MCPServerManager (cognitive 30) · ×1
  • MCPServerManager.MCPServerManager (cognitive 30) apps/agent_web/frontend/src/components/MCPServerManager.tsx:23 — MCPServerManager.MCPServerManager has cognitive complexity 30 (threshold 15). Drivers by points: boolean chains 14, error handling 4 (5 pts), ternaries 4 (5 pts), if/else 4, match/switch 2 (nesting depth added 2). Most of this is not in the body itself: 11 of the 30 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 221, handleToggleServer, handleDeleteServer, …). 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.
D2 · Cognitive Complexity · mcp_client_v2.send_message (cognitive 29) · ×1
  • mcp_client_v2.send_message (cognitive 29) apps/agent_web/src/mcp_client_v2.erl:733 — mcp_client_v2.send_message has cognitive complexity 29 (threshold 15). Drivers by points: match/switch 14 (26 pts), error handling 2 (3 pts) (nesting depth added 13). 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.
D2 · Cognitive Complexity · agent_dynamic_system.handle_call (cognitive 29) · ×1
  • agent_dynamic_system.handle_call (cognitive 29) apps/agents/src/agent_dynamic_system.erl:104 — agent_dynamic_system.handle_call has cognitive complexity 29 (threshold 15). Drivers by points: match/switch 19 (25 pts), if/else 1 (2 pts), error handling 1, loops 1 (nesting depth added 7). 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.
D2 · Cognitive Complexity · AdvancedStructuredOutputsManager.AdvancedStructuredOutputsManager (cognitive 29) · ×1
  • AdvancedStructuredOutputsManager.AdvancedStructuredOutputsManager (cognitive 29) apps/agent_web/frontend/src/components/AdvancedStructuredOutputsManager.tsx:62 — AdvancedStructuredOutputsManager.AdvancedStructuredOutputsManager has cognitive complexity 29 (threshold 15). Drivers by points: boolean chains 13, ternaries 5 (6 pts), error handling 4, if/else 4, match/switch 2 (nesting depth added 1). Most of this is not in the body itself: 9 of the 29 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 75, a function literal at line 133, a function literal at line 96, …). 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.
D2 · Cognitive Complexity · streaming_function_handler.process_token_for_display (cognitive 28) · ×1
  • streaming_function_handler.process_token_for_display (cognitive 28) apps/agents/src/streaming_function_handler.erl:458 — streaming_function_handler.process_token_for_display has cognitive complexity 28 (threshold 15). Drivers by points: match/switch 11 (18 pts), error handling 2 (6 pts), boolean chains 3, if/else 1 (nesting depth added 11). 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.
D2 · Cognitive Complexity · MultiAgentChat.MultiAgentChat (cognitive 28) · ×1
  • MultiAgentChat.MultiAgentChat (cognitive 28) apps/agent_web/frontend/src/components/MultiAgentChat.tsx:39 — MultiAgentChat.MultiAgentChat has cognitive complexity 28 (threshold 15). Drivers by points: boolean chains 11, ternaries 8 (10 pts), if/else 6 (7 pts) (nesting depth added 3). Most of this is not in the body itself: 13 of the 28 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 54, createGroupChat, closeChatSession, …). 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.
D2 · Cognitive Complexity · MultiAgentChat.GroupChatInterface (cognitive 28) · ×1
  • MultiAgentChat.GroupChatInterface (cognitive 28) apps/agent_web/frontend/src/components/MultiAgentChat.tsx:351 — MultiAgentChat.GroupChatInterface has cognitive complexity 28 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 7, error handling 2 (5 pts), ternaries 4 (nesting depth added 8). Most of this is not in the body itself: 1 of the 28 points is its own statement and the rest belongs to 6 function items inside it that branch (sendToGroup, a function literal at line 392, a function literal at line 484, …). 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.
D2 · Cognitive Complexity · AdaptiveAIInterface.AdaptiveAIInterface (cognitive 28) · ×1
  • AdaptiveAIInterface.AdaptiveAIInterface (cognitive 28) apps/agent_web/frontend/src/components/AdaptiveAIInterface.tsx:46 — AdaptiveAIInterface.AdaptiveAIInterface has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 22 (27 pts), if/else 1 (nesting depth added 5). Most of this is not in the body itself: 5 of the 28 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 131, 212, 205, …). 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.
D2 · Cognitive Complexity · mcp_orchestration_handler.handle_request (cognitive 27) · ×1
  • mcp_orchestration_handler.handle_request (cognitive 27) apps/agent_web/src/mcp_orchestration_handler.erl:15 — mcp_orchestration_handler.handle_request has cognitive complexity 27 (threshold 15). Drivers by points: match/switch 19 (24 pts), loops 1 (3 pts) (nesting depth added 7). 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.
D2 · Cognitive Complexity · ResourceSentinelBar.ResourceSentinelBar (cognitive 27) · ×1
  • ResourceSentinelBar.ResourceSentinelBar (cognitive 27) apps/agent_web/frontend/src/components/ResourceSentinelBar.tsx:30 — ResourceSentinelBar.ResourceSentinelBar has cognitive complexity 27 (threshold 15). Drivers by points: ternaries 7 (16 pts), if/else 5 (9 pts), match/switch 2 (nesting depth added 13). Most of this is not in the body itself: 1 of the 27 points is its own statement and the rest belongs to 3 function items inside it that branch (a function literal at line 38, getThresholdColor, getTrendIcon). 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.
D2 · Cognitive Complexity · agent_web_app.health_monitor (cognitive 25) · ×1
  • agent_web_app.health_monitor (cognitive 25) apps/agent_web/src/agent_web_app.erl:149 — agent_web_app.health_monitor has cognitive complexity 25 (threshold 15). Drivers by points: error handling 5 (12 pts), match/switch 4 (7 pts), if/else 2 (4 pts), loops 1 (2 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.
D2 · Cognitive Complexity · hyper_graph_storage.handle_call (cognitive 25) · ×1
  • hyper_graph_storage.handle_call (cognitive 25) apps/agent_web/src/hyper_graph_storage.erl:125 — hyper_graph_storage.handle_call has cognitive complexity 25 (threshold 15). Drivers by points: error handling 11 (15 pts), match/switch 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.
D2 · Cognitive Complexity · pipedream_auth_handler.handle_call (cognitive 25) · ×1
  • pipedream_auth_handler.handle_call (cognitive 25) apps/agent_web/src/pipedream_auth_handler.erl:68 — pipedream_auth_handler.handle_call has cognitive complexity 25 (threshold 15). Drivers by points: match/switch 15 (19 pts), loops 3 (5 pts), if/else 1 (nesting depth added 6). 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.
D2 · Cognitive Complexity · sanitize.cleanNode (cognitive 25) · ×1
  • sanitize.cleanNode (cognitive 25) apps/agent_web/frontend/src/utils/sanitize.ts:30 — sanitize.cleanNode has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 4, error handling 1 (3 pts), loops 1 (3 pts) (nesting depth added 12). Most of this is not in the body itself: 9 of the 25 points are its own statements and the rest belongs to one function literal inside it that branches (line 51). 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.
D2 · Cognitive Complexity · agent_tools.evaluate_math_expression (cognitive 24) · ×1
  • agent_tools.evaluate_math_expression (cognitive 24) apps/agents/src/agent_tools.erl:3217 — agent_tools.evaluate_math_expression has cognitive complexity 24 (threshold 15). Drivers by points: match/switch 8 (18 pts), error handling 3 (6 pts) (nesting depth added 13). 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.
D2 · Cognitive Complexity · agent_ws_handler.websocket_handle (cognitive 23) · ×1
  • agent_ws_handler.websocket_handle (cognitive 23) apps/agent_web/src/agent_ws_handler.erl:22 — agent_ws_handler.websocket_handle has cognitive complexity 23 (threshold 15). Drivers by points: match/switch 11 (19 pts), error handling 2 (4 pts) (nesting depth added 10). 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.
D2 · Cognitive Complexity · agent_tool_registry.handle_call (cognitive 23) · ×1
  • agent_tool_registry.handle_call (cognitive 23) apps/agents/src/agent_tool_registry.erl:96 — agent_tool_registry.handle_call has cognitive complexity 23 (threshold 15). Drivers by points: match/switch 11 (12 pts), if/else 3 (6 pts), loops 4, boolean chains 1 (nesting depth added 4). 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.
D2 · Cognitive Complexity · meta_server.execute_meta_command_impl (cognitive 23) · ×1
  • meta_server.execute_meta_command_impl (cognitive 23) apps/agents/src/meta_server.erl:727 — meta_server.execute_meta_command_impl has cognitive complexity 23 (threshold 15). Drivers by points: match/switch 14 (17 pts), error handling 3 (6 pts) (nesting depth added 6). 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.
D2 · Cognitive Complexity · InteractiveReasoningControls.InteractiveReasoningControls (cognitive 23) · ×1
  • InteractiveReasoningControls.InteractiveReasoningControls (cognitive 23) apps/agent_web/frontend/src/components/InteractiveReasoningControls.tsx:53 — InteractiveReasoningControls.InteractiveReasoningControls has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 11, if/else 5, error handling 4, ternaries 3. Most of this is not in the body itself: 8 of the 23 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 112, 158, 193, …). 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.
D2 · Cognitive Complexity · streaming_function_handler.log_safe (cognitive 22) · ×1
  • streaming_function_handler.log_safe (cognitive 22) apps/agents/src/streaming_function_handler.erl:420 — streaming_function_handler.log_safe has cognitive complexity 22 (threshold 15). Drivers by points: match/switch 8 (15 pts), error handling 3 (7 pts) (nesting depth added 11). 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.
D2 · Cognitive Complexity · openai_streaming.log_safe (cognitive 22) · ×1
  • openai_streaming.log_safe (cognitive 22) apps/openai/src/openai_streaming.erl:162 — openai_streaming.log_safe has cognitive complexity 22 (threshold 15). Drivers by points: match/switch 8 (15 pts), error handling 3 (7 pts) (nesting depth added 11). 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.
D2 · Cognitive Complexity · SimpleAdvancedChat.AdvancedMessageContent (cognitive 22) · ×1
  • SimpleAdvancedChat.AdvancedMessageContent (cognitive 22) REDACTED:77 — SimpleAdvancedChat.AdvancedMessageContent has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 13 (15 pts), boolean chains 5, error handling 1, match/switch 1 (nesting depth added 2). Most of this is not in the body itself: 2 of the 22 points are its own statements and the rest belongs to 4 function items inside it that branch (renderMarkdown, renderJSON, renderHTML, …). 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.
D2 · Cognitive Complexity · agent_api_handler.list_agents (cognitive 21) · ×1
  • agent_api_handler.list_agents (cognitive 21) apps/agent_web/src/agent_api_handler.erl:90 — agent_api_handler.list_agents has cognitive complexity 21 (threshold 15). Drivers by points: match/switch 10 (15 pts), error handling 2 (6 pts) (nesting depth added 9). 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.
D2 · Cognitive Complexity · auto_healing_startup.ensure_all_systems_running (cognitive 21) · ×1
  • auto_healing_startup.ensure_all_systems_running (cognitive 21) apps/agent_web/src/auto_healing_startup.erl:8 — auto_healing_startup.ensure_all_systems_running has cognitive complexity 21 (threshold 15). Drivers by points: match/switch 12 (19 pts), error handling 1 (2 pts) (nesting depth added 8). 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.
D2 · Cognitive Complexity · conversation_handler.handle_post (cognitive 21) · ×1
  • conversation_handler.handle_post (cognitive 21) apps/agent_web/src/conversation_handler.erl:57 — conversation_handler.handle_post has cognitive complexity 21 (threshold 15). Drivers by points: match/switch 7 (14 pts), error handling 2 (5 pts), if/else 2 (nesting depth added 10). 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.
D2 · Cognitive Complexity · agent_collaboration.handle_call (cognitive 21) · ×1
  • agent_collaboration.handle_call (cognitive 21) apps/agents/src/agent_collaboration.erl:83 — agent_collaboration.handle_call has cognitive complexity 21 (threshold 15). Drivers by points: match/switch 18 (21 pts) (nesting depth added 3). 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.
D2 · Cognitive Complexity · mcp_connection_manager.handle_call (cognitive 20) · ×1
  • mcp_connection_manager.handle_call (cognitive 20) apps/agent_web/src/mcp_connection_manager.erl:91 — mcp_connection_manager.handle_call has cognitive complexity 20 (threshold 15). Drivers by points: match/switch 8 (12 pts), error handling 3 (8 pts) (nesting depth added 9). 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.
D2 · Cognitive Complexity · realtime_metrics_engine.analyze_q_table (cognitive 20) · ×1
  • realtime_metrics_engine.analyze_q_table (cognitive 20) apps/agent_web/src/realtime_metrics_engine.erl:605 — realtime_metrics_engine.analyze_q_table has cognitive complexity 20 (threshold 15). Drivers by points: match/switch 8 (11 pts), loops 3 (6 pts), if/else 1 (3 pts) (nesting depth added 8). 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.
D2 · Cognitive Complexity · jina_tools.jina_classify (cognitive 20) · ×1
  • jina_tools.jina_classify (cognitive 20) apps/agents/src/jina_tools.erl:570 — jina_tools.jina_classify has cognitive complexity 20 (threshold 15). Drivers by points: match/switch 6 (10 pts), loops 4 (6 pts), if/else 2 (4 pts) (nesting depth added 8). 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.
D2 · Cognitive Complexity · mcp_client_v2.start_websocket_connection (cognitive 19) · ×1
  • mcp_client_v2.start_websocket_connection (cognitive 19) apps/agent_web/src/mcp_client_v2.erl:300 — mcp_client_v2.start_websocket_connection has cognitive complexity 19 (threshold 15). Drivers by points: match/switch 8 (17 pts), boolean chains 2 (nesting depth added 9). 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.
D2 · Cognitive Complexity · openapi_introspection.handle_call (cognitive 19) · ×1
  • openapi_introspection.handle_call (cognitive 19) apps/openapi_scaffold/src/openapi_introspection.erl:49 — openapi_introspection.handle_call has cognitive complexity 19 (threshold 15). Drivers by points: match/switch 10 (16 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 7). 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.
D2 · Cognitive Complexity · DenseDashboard.DenseDashboard (cognitive 19) · ×1
  • DenseDashboard.DenseDashboard (cognitive 19) apps/agent_web/frontend/src/components/DenseDashboard.tsx:15 — DenseDashboard.DenseDashboard has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 15, ternaries 3 (4 pts) (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 5 function literals inside it that branch (lines 85, 36, 16, …). 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.
D2 · Cognitive Complexity · conversation_stats_logger.display_periodic_stats (cognitive 18) · ×1
  • conversation_stats_logger.display_periodic_stats (cognitive 18) apps/agent_web/src/conversation_stats_logger.erl:276 — conversation_stats_logger.display_periodic_stats has cognitive complexity 18 (threshold 15). Drivers by points: match/switch 12 (16 pts), if/else 2 (nesting depth added 4). 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.
D2 · Cognitive Complexity · mcp_manager.handle_call (cognitive 18) · ×1
  • mcp_manager.handle_call (cognitive 18) apps/agent_web/src/mcp_manager.erl:249 — mcp_manager.handle_call has cognitive complexity 18 (threshold 15). Drivers by points: match/switch 15 (18 pts) (nesting depth added 3). 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.
D2 · Cognitive Complexity · ssl_cert_handler.validate_cert_key_match (cognitive 18) · ×1
  • ssl_cert_handler.validate_cert_key_match (cognitive 18) apps/agent_web/src/ssl_cert_handler.erl:162 — ssl_cert_handler.validate_cert_key_match has cognitive complexity 18 (threshold 15). Drivers by points: match/switch 6 (12 pts), error handling 2 (6 pts) (nesting depth added 10). 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.
D2 · Cognitive Complexity · dynamic_supervisor_manager.handle_call (cognitive 18) · ×1
  • dynamic_supervisor_manager.handle_call (cognitive 18) apps/agents/src/dynamic_supervisor_manager.erl:78 — dynamic_supervisor_manager.handle_call has cognitive complexity 18 (threshold 15). Drivers by points: match/switch 13 (18 pts) (nesting depth added 5). 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.
D2 · Cognitive Complexity · lockfree_coordination.lockfree_dequeue_loop (cognitive 18) · ×1
  • lockfree_coordination.lockfree_dequeue_loop (cognitive 18) apps/agents/src/lockfree_coordination.erl:384 — lockfree_coordination.lockfree_dequeue_loop has cognitive complexity 18 (threshold 15). Drivers by points: match/switch 10 (18 pts) (nesting depth added 8). 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.
D2 · Cognitive Complexity · Dashboard.Dashboard (cognitive 18) · ×1
  • Dashboard.Dashboard (cognitive 18) REDACTED:47 — Dashboard.Dashboard has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 10, ternaries 4 (5 pts), if/else 3 (nesting depth added 1). Of this number, 15 points are the body's own statements and 3 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.
D2 · Cognitive Complexity · ai_log_integration.detect_and_analyze_error (cognitive 17) · ×1
  • ai_log_integration.detect_and_analyze_error (cognitive 17) apps/agent_web/src/ai_log_integration.erl:269 — ai_log_integration.detect_and_analyze_error has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 8 (17 pts) (nesting depth added 9). 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.
D2 · Cognitive Complexity · mcp_connection_manager.start_new_connection (cognitive 17) · ×1
  • mcp_connection_manager.start_new_connection (cognitive 17) apps/agent_web/src/mcp_connection_manager.erl:295 — mcp_connection_manager.start_new_connection has cognitive complexity 17 (threshold 15). Drivers by points: error handling 5 (14 pts), match/switch 2 (3 pts) (nesting depth added 10). 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.
D2 · Cognitive Complexity · mcp_manager.connect_configured_server (cognitive 17) · ×1
  • mcp_manager.connect_configured_server (cognitive 17) apps/agent_web/src/mcp_manager.erl:546 — mcp_manager.connect_configured_server has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 4 (10 pts), error handling 2 (5 pts), boolean chains 1, if/else 1 (nesting depth added 9). 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.
D2 · Cognitive Complexity · mcp_manager.parse_websocket_url (cognitive 17) · ×1
  • mcp_manager.parse_websocket_url (cognitive 17) apps/agent_web/src/mcp_manager.erl:917 — mcp_manager.parse_websocket_url has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 5 (11 pts), error handling 2 (6 pts) (nesting depth added 10). 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.
D2 · Cognitive Complexity · mcp_oauth_client.handle_call (cognitive 17) · ×1
  • mcp_oauth_client.handle_call (cognitive 17) apps/agent_web/src/mcp_oauth_client.erl:60 — mcp_oauth_client.handle_call has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 9 (14 pts), if/else 3 (nesting depth added 5). 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.
D2 · Cognitive Complexity · CommandPalette.CommandPalette (cognitive 17) · ×1
  • CommandPalette.CommandPalette (cognitive 17) apps/agent_web/frontend/src/components/CommandPalette.tsx:28 — CommandPalette.CommandPalette has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 15, if/else 1, match/switch 1. Of this number, 9 points are the body's own statements and 8 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.
D2 · Cognitive Complexity · knowledge_base_handler.handle_request (cognitive 16) · ×1
  • knowledge_base_handler.handle_request (cognitive 16) apps/agent_web/src/knowledge_base_handler.erl:11 — knowledge_base_handler.handle_request has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 14 (16 pts) (nesting depth added 2). 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.
D2 · Cognitive Complexity · mcp_oauth_handler.handle_request (cognitive 16) · ×1
  • mcp_oauth_handler.handle_request (cognitive 16) apps/agent_web/src/mcp_oauth_handler.erl:21 — mcp_oauth_handler.handle_request has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 12 (16 pts) (nesting depth added 4). 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.
D2 · Cognitive Complexity · oauth_manager.handle_call (cognitive 16) · ×1
  • oauth_manager.handle_call (cognitive 16) apps/agent_web/src/oauth_manager.erl:94 — oauth_manager.handle_call has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 8 (13 pts), error handling 1, if/else 1, loops 1 (nesting depth added 5). 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.
D2 · Cognitive Complexity · ssl_cert_handler.check_expiry (cognitive 16) · ×1
  • ssl_cert_handler.check_expiry (cognitive 16) apps/agent_web/src/ssl_cert_handler.erl:199 — ssl_cert_handler.check_expiry has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 6 (16 pts) (nesting depth added 10). 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.
D2 · Cognitive Complexity · agent.mcp_agent_process (cognitive 16) · ×1
  • agent.mcp_agent_process (cognitive 16) apps/agents/src/agent.erl:242 — agent.mcp_agent_process has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 5 (15 pts), error handling 1 (nesting depth added 10). 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.
D2 · Cognitive Complexity · agent_tools.execute_database_query (cognitive 16) · ×1
  • agent_tools.execute_database_query (cognitive 16) apps/agents/src/agent_tools.erl:3558 — agent_tools.execute_database_query has cognitive complexity 16 (threshold 15). Drivers by points: loops 2 (7 pts), match/switch 3 (5 pts), error handling 2 (4 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · agent_tools.handle_call (cognitive 16) · ×1
  • agent_tools.handle_call (cognitive 16) apps/agents/src/agent_tools.erl:134 — agent_tools.handle_call has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 8 (10 pts), error handling 4 (6 pts) (nesting depth added 4). 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.
D2 · Cognitive Complexity · swarm_intelligence_engine.handle_call (cognitive 16) · ×1
  • swarm_intelligence_engine.handle_call (cognitive 16) apps/agents/src/swarm_intelligence_engine.erl:131 — swarm_intelligence_engine.handle_call has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 13 (16 pts) (nesting depth added 3). 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.
D2 · Cognitive Complexity · token_stream_fsm.streaming (cognitive 16) · ×1
  • token_stream_fsm.streaming (cognitive 16) apps/openai/src/token_stream_fsm.erl:244 — token_stream_fsm.streaming has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 9 (16 pts) (nesting depth added 7). 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.
D2 · Cognitive Complexity · SeedServersDialog.SeedServersDialog (cognitive 16) · ×1
  • SeedServersDialog.SeedServersDialog (cognitive 16) apps/agent_web/frontend/src/components/SeedServersDialog.tsx:116 — SeedServersDialog.SeedServersDialog has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 3 (6 pts), boolean chains 3, error handling 2 (3 pts), if/else 2, match/switch 2 (nesting depth added 4). None of this is in the body itself: all 16 points belong to 4 function items inside it that branch (addServer, a function literal at line 212, getAuthIcon, …). 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.
D2 · Cognitive Complexity · TokenHeatmap.TokenHeatmap (cognitive 16) · ×1
  • TokenHeatmap.TokenHeatmap (cognitive 16) apps/agent_web/frontend/src/components/TokenHeatmap.tsx:22 — TokenHeatmap.TokenHeatmap has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7, ternaries 4 (5 pts), boolean chains 2, loops 2 (nesting depth added 1). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 7 function items inside it that branch (getIntensityColor, generateMockData, a function literal at line 31, …). 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.
D30 · Dependency Vulnerabilities · Medium vulnerability · ×1
  • REDACTED
D4 · Code Duplication · Near-duplicate member family (3 members, 38 shared lines) · ×1
  • Near-duplicate member family (3 members, 38 shared lines) apps/agent_web/src/mcp_server.erl:285 — apps/agent_web/src/mcp_server.erl:285-470 | apps/agents/src/agent_tools.erl:1846-2130 | apps/agents/src/jina_tools.erl:14-299 — These 3 members are variants of one another: a block of 38 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 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 3 times.
D4 · Code Duplication · Near-duplicate member pair (73 shared lines) · ×1
  • Near-duplicate member pair (73 shared lines) apps/agent_web/src/consciousness_bridge_api_handler.erl:103 — apps/agent_web/src/consciousness_bridge_api_handler.erl:103-245 | apps/agent_web/src/neural_swarm_api_handler.erl:89-226 — These two members are variants of one another: 73 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 · Near-duplicate member pair (32 shared lines) · ×1
  • Near-duplicate member pair (32 shared lines) apps/agent_web/src/pipedream_mcp_client.erl:207 — apps/agent_web/src/pipedream_mcp_client.erl:207-246 | apps/agent_web/src/pipedream_mcp_client.erl:248-284 — These two members are variants of one another: 32 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 · Edited copy of a member (26 corresponding lines) · ×1
  • Edited copy of a member (26 corresponding lines) apps/agents/src/agent_registry.erl:111 — apps/agents/src/agent_registry.erl:111-136 | sandbox/myapp/apps/myapp/src/agent_registry.erl:108-133 — These two members are one piece of code written twice and then edited apart: 26 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) apps/agent_web/src/mcp_client_v2.erl:389 — apps/agent_web/src/mcp_client_v2.erl:389-422 | apps/agent_web/src/mcp_client_v2.erl:500-518 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Members sharing a duplicated core (8 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (8 members, 50+ identical tokens) apps/openai/src/openai_files.erl:271 — apps/openai/src/openai_files.erl:271-296 | apps/openai/src/openai_files.erl:298-323 | apps/openai/src/openai_files.erl:325-355 | apps/openai/src/openai_responses.erl:204-250 | apps/openai/src/openai_responses.erl:285-320 | apps/openai/src/openai_responses.erl:322-350 | apps/openai/src/openai_responses.erl:352-380 | apps/openai/src/openai_responses.erl:382-417 — These 8 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 8 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 8 times.
D4 · Code Duplication · Members sharing a duplicated core (7 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (7 members, 50+ identical tokens) apps/agents/src/jina_tools.erl:305 — apps/agents/src/jina_tools.erl:305-359 | apps/agents/src/jina_tools.erl:361-397 | apps/agents/src/jina_tools.erl:399-434 | apps/agents/src/jina_tools.erl:531-568 | apps/agents/src/jina_tools.erl:570-624 | apps/agents/src/jina_tools.erl:626-657 | apps/agents/src/jina_tools.erl:659-705 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
D4 · Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (6 members, 50+ identical tokens) apps/agent_web/src/ai_error_interpreter.erl:158 — apps/agent_web/src/ai_error_interpreter.erl:158-188 | apps/agent_web/src/ai_error_interpreter.erl:202-223 | apps/agent_web/src/ai_timeout_analyzer.erl:254-285 | apps/agent_web/src/ai_timeout_analyzer.erl:493-521 | apps/agent_web/src/crash_ai_analyzer.erl:91-119 | apps/agent_web/src/crash_ai_analyzer.erl:161-186 — 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 (5 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (5 members, 50+ identical tokens) apps/agent_web/src/model_api_handler.erl:150 — apps/agent_web/src/model_api_handler.erl:150-209 | apps/agent_web/src/model_api_handler.erl:224-287 | apps/agent_web/src/model_api_handler.erl:302-341 | apps/agent_web/src/model_api_handler.erl:450-490 | apps/agent_web/src/model_api_handler.erl:492-535 — 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 · Duplicated block (138 lines × 2) · ×1
  • Duplicated block (138 lines × 2) apps/agents/src/agent_discovery.erl:133 — apps/agents/src/agent_discovery.erl:133-270 | sandbox/myapp/apps/myapp/src/agent_discovery.erl:139-276 — before extracting anything, compare `apps/agents/src/agent_discovery.erl` and `sandbox/myapp/apps/myapp/src/agent_discovery.erl` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 382 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.
D4 · Code Duplication · Duplicated block (54 lines × 2) · ×1
  • Duplicated block (54 lines × 2) apps/agents/src/agent_messenger.erl:83 — apps/agents/src/agent_messenger.erl:83-136 | sandbox/myapp/apps/myapp/src/agent_messenger.erl:83-136 — before extracting anything, compare `apps/agents/src/agent_messenger.erl` and `sandbox/myapp/apps/myapp/src/agent_messenger.erl` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 97 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.
D4 · Code Duplication · Duplicated block (53 lines × 2) · ×1
  • Duplicated block (53 lines × 2) apps/agents/src/agent_tools.erl:134 — apps/agents/src/agent_tools.erl:134-186 | sandbox/myapp/apps/myapp/src/agent_tools.erl:92-144 — before extracting anything, compare `apps/agents/src/agent_tools.erl` and `sandbox/myapp/apps/myapp/src/agent_tools.erl` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 223 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.
D4 · Code Duplication · Duplicated block (44 lines × 2) · ×1
  • Duplicated block (44 lines × 2) apps/agents/src/agent_discovery.erl:294 — apps/agents/src/agent_discovery.erl:294-337 | sandbox/myapp/apps/myapp/src/agent_discovery.erl:310-353 — before extracting anything, compare `apps/agents/src/agent_discovery.erl` and `sandbox/myapp/apps/myapp/src/agent_discovery.erl` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 382 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.
D4 · Code Duplication · Duplicated block (42 lines × 2) · ×1
  • Duplicated block (42 lines × 2) apps/agents/src/agent_tools.erl:1760 — apps/agents/src/agent_tools.erl:1760-1801 | sandbox/myapp/apps/myapp/src/agent_tools.erl:339-380 — before extracting anything, compare `apps/agents/src/agent_tools.erl` and `sandbox/myapp/apps/myapp/src/agent_tools.erl` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 223 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.
D4 · Code Duplication · Duplicated block (34 lines × 2) · ×1
  • Duplicated block (34 lines × 2) apps/agents/src/agent_discovery.erl:471 — apps/agents/src/agent_discovery.erl:471-504 | sandbox/myapp/apps/myapp/src/agent_discovery.erl:487-520 — before extracting anything, compare `apps/agents/src/agent_discovery.erl` and `sandbox/myapp/apps/myapp/src/agent_discovery.erl` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 382 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.
D4 · Code Duplication · Duplicated block (29 lines × 2) · ×1
  • Duplicated block (29 lines × 2) apps/agents/src/timeline_event_store.erl:280 — apps/agents/src/timeline_event_store.erl:280-308 | apps/agents/src/timeline_event_store.erl:315-343 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (27 lines × 2) · ×1
  • Duplicated block (27 lines × 2) apps/agents/src/hello_world.erl:18 — apps/agents/src/hello_world.erl:18-44 | sandbox/myapp/apps/myapp/src/hello_world.erl:18-44 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (23–26 lines × 4) · ×1
  • Duplicated block (23–26 lines × 4) apps/agents/src/agent_discovery.erl:492 — apps/agents/src/agent_discovery.erl:492-517 | apps/agents/src/agent_discovery.erl:532-554 | sandbox/myapp/apps/myapp/src/agent_discovery.erl:508-533 | sandbox/myapp/apps/myapp/src/agent_discovery.erl:548-570 — before extracting anything, compare `apps/agents/src/agent_discovery.erl` and `sandbox/myapp/apps/myapp/src/agent_discovery.erl` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 382 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.
D4 · Code Duplication · Duplicated block (26 lines × 2) · ×1
  • Duplicated block (26 lines × 2) apps/openai/src/openai_chat.erl:66 — apps/openai/src/openai_chat.erl:66-91 | apps/openai/src/openai_responses.erl:103-128 — before extracting anything, compare `apps/openai/src/openai_chat.erl` and `apps/openai/src/openai_responses.erl` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (25 lines × 2) · ×1
  • Duplicated block (25 lines × 2) apps/agents/src/agent_tools.erl:378 — apps/agents/src/agent_tools.erl:378-402 | sandbox/myapp/apps/myapp/src/agent_tools.erl:237-261 — before extracting anything, compare `apps/agents/src/agent_tools.erl` and `sandbox/myapp/apps/myapp/src/agent_tools.erl` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 223 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.
D4 · Code Duplication · Duplicated block (23–24 lines × 2) · ×1
  • Duplicated block (23–24 lines × 2) apps/agents/src/agent_tools.erl:2103 — apps/agents/src/agent_tools.erl:2103-2125 | apps/agents/src/jina_tools.erl:227-250 — before extracting anything, compare `apps/agents/src/agent_tools.erl` and `apps/agents/src/jina_tools.erl` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 201 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (23 lines × 2) · ×1
  • Duplicated block (23 lines × 2) apps/agents/src/agent.erl:150 — apps/agents/src/agent.erl:150-172 | sandbox/myapp/apps/myapp/src/agent.erl:73-95 — before extracting anything, compare `apps/agents/src/agent.erl` and `sandbox/myapp/apps/myapp/src/agent.erl` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 154 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.
D4 · Code Duplication · Duplicated block (22–23 lines × 2) · ×1
  • Duplicated block (22–23 lines × 2) apps/agents/src/agent_tools.erl:2043 — apps/agents/src/agent_tools.erl:2043-2064 | apps/agents/src/jina_tools.erl:171-193 — before extracting anything, compare `apps/agents/src/agent_tools.erl` and `apps/agents/src/jina_tools.erl` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 201 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (20–21 lines × 2) · ×1
  • Duplicated block (20–21 lines × 2) apps/agents/src/agent_tools.erl:2074 — apps/agents/src/agent_tools.erl:2074-2093 | apps/agents/src/jina_tools.erl:200-220 — before extracting anything, compare `apps/agents/src/agent_tools.erl` and `apps/agents/src/jina_tools.erl` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 201 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (19 lines × 4) · ×1
  • Duplicated block (19 lines × 4) apps/agent_web/src/mcp_client_v2.erl:132 — apps/agent_web/src/mcp_client_v2.erl:132-150 | apps/agent_web/src/mcp_client_v2.erl:168-186 | apps/agent_web/src/mcp_client_v2.erl:331-349 | apps/agent_web/src/mcp_client_v2.erl:920-938 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (18–19 lines × 2) · ×1
  • Duplicated block (18–19 lines × 2) apps/agents/src/agent_quorum.erl:110 — apps/agents/src/agent_quorum.erl:110-127 | apps/agents/src/agent_quorum.erl:186-204 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (17–18 lines × 8) · ×1
  • Duplicated block (17–18 lines × 8) apps/openai/src/openai_files.erl:280 — apps/openai/src/openai_files.erl:280-296 | apps/openai/src/openai_files.erl:307-323 | apps/openai/src/openai_files.erl:339-355 | apps/openai/src/openai_responses.erl:233-250 | apps/openai/src/openai_responses.erl:304-320 | apps/openai/src/openai_responses.erl:334-350 | apps/openai/src/openai_responses.erl:364-380 | apps/openai/src/openai_responses.erl:401-417 — there are 8 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 8 sites; resolving a subset leaves the remainder to drift apart.
D4 · Code Duplication · Duplicated block (18 lines × 3) · ×1
  • Duplicated block (18 lines × 3) apps/openai/src/token_stream_fsm.erl:583 — apps/openai/src/token_stream_fsm.erl:583-600 | apps/openai/src/token_stream_handler.erl:411-428 | apps/openai/src/token_stream_integration.erl:403-420 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (14–18 lines × 2) · ×1
  • Duplicated block (14–18 lines × 2) apps/agents/src/self_replicating_supervisor.erl:304 — apps/agents/src/self_replicating_supervisor.erl:304-321 | apps/agents/src/self_replicating_supervisor.erl:414-427 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (14–16 lines × 4) · ×1
  • Duplicated block (14–16 lines × 4) apps/agents/src/agent_discovery.erl:390 — apps/agents/src/agent_discovery.erl:390-405 | apps/agents/src/agent_discovery.erl:428-441 | sandbox/myapp/apps/myapp/src/agent_discovery.erl:406-421 | sandbox/myapp/apps/myapp/src/agent_discovery.erl:444-457 — before extracting anything, compare `apps/agents/src/agent_discovery.erl` and `sandbox/myapp/apps/myapp/src/agent_discovery.erl` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 382 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.
D4 · Code Duplication · Duplicated block (15–16 lines × 2) · ×1
  • Duplicated block (15–16 lines × 2) apps/agents/src/agent_tools.erl:1861 — apps/agents/src/agent_tools.erl:1861-1875 | apps/agents/src/agent_tools.erl:1901-1916 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (14–15 lines × 4) · ×1
  • Duplicated block (14–15 lines × 4) apps/agent_web/src/mcp_oauth_handler.erl:30 — apps/agent_web/src/mcp_oauth_handler.erl:30-43 | apps/agent_web/src/mcp_oauth_handler.erl:101-114 | apps/agent_web/src/mcp_oauth_handler.erl:149-163 | apps/agent_web/src/mcp_oauth_handler.erl:183-196 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (14 lines × 4) · ×1
  • Duplicated block (14 lines × 4) apps/agents/src/agent.erl:625 — apps/agents/src/agent.erl:625-638 | apps/agents/src/simple_agent.erl:133-146 | sandbox/myapp/apps/myapp/src/agent.erl:208-221 | sandbox/myapp/apps/myapp/src/simple_agent.erl:102-115 — before extracting anything, compare `apps/agents/src/agent.erl` and `sandbox/myapp/apps/myapp/src/agent.erl` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 154 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.
D4 · Code Duplication · Duplicated block (13–14 lines × 3) · ×1
  • Duplicated block (13–14 lines × 3) apps/agent_web/src/mcp_client_v2.erl:409 — apps/agent_web/src/mcp_client_v2.erl:409-422 | apps/agent_web/src/mcp_transport.erl:168-180 | apps/agent_web/src/mcp_transport.erl:227-239 — before extracting anything, compare `apps/agent_web/src/mcp_client_v2.erl` and `apps/agent_web/src/mcp_transport.erl` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (14 lines × 3) · ×1
  • Duplicated block (14 lines × 3) apps/agent_web/src/model_api_handler.erl:188 — apps/agent_web/src/model_api_handler.erl:188-201 | apps/agent_web/src/model_api_handler.erl:266-279 | apps/agent_web/src/model_api_handler.erl:469-482 — 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.
D4 · Code Duplication · Duplicated block (13 lines × 7) · ×1
  • Duplicated block (13 lines × 7) apps/agents/src/jina_tools.erl:343 — apps/agents/src/jina_tools.erl:343-355 | apps/agents/src/jina_tools.erl:381-393 | apps/agents/src/jina_tools.erl:418-430 | apps/agents/src/jina_tools.erl:551-563 | apps/agents/src/jina_tools.erl:607-619 | apps/agents/src/jina_tools.erl:641-653 | apps/agents/src/jina_tools.erl:689-701 — all 7 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (11–13 lines × 2) · ×1
  • Duplicated block (11–13 lines × 2) apps/agents/src/agent_tools.erl:348 — apps/agents/src/agent_tools.erl:348-358 | sandbox/myapp/apps/myapp/src/agent_tools.erl:189-201 — before extracting anything, compare `apps/agents/src/agent_tools.erl` and `sandbox/myapp/apps/myapp/src/agent_tools.erl` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 223 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.
D4 · Code Duplication · Duplicated block (12–13 lines × 2) · ×1
  • Duplicated block (12–13 lines × 2) apps/openai/src/openai_chat.erl:187 — apps/openai/src/openai_chat.erl:187-198 | apps/openai/src/openai_chat.erl:310-322 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (12 lines × 4) · ×1
  • Duplicated block (12 lines × 4) apps/agent_web/src/fleet_management_handler.erl:22 — apps/agent_web/src/fleet_management_handler.erl:22-33 | apps/agent_web/src/fleet_management_handler.erl:41-52 | apps/agent_web/src/fleet_management_handler.erl:60-71 | apps/agent_web/src/fleet_management_handler.erl:87-98 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (11–12 lines × 2) · ×1
  • Duplicated block (11–12 lines × 2) apps/agent_web/src/mcp_server.erl:452 — apps/agent_web/src/mcp_server.erl:452-463 | apps/agents/src/jina_tools.erl:257-267 — before extracting anything, compare `apps/agent_web/src/mcp_server.erl` and `apps/agents/src/jina_tools.erl` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 62 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.
D4 · Code Duplication · Duplicated block (11 lines × 4) · ×1
  • Duplicated block (11 lines × 4) apps/agent_web/src/mcp_orchestration_handler.erl:82 — apps/agent_web/src/mcp_orchestration_handler.erl:82-92 | apps/agent_web/src/mcp_orchestration_handler.erl:102-112 | apps/agent_web/src/mcp_orchestration_handler.erl:126-136 | apps/agent_web/src/mcp_orchestration_handler.erl:149-159 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (11 lines × 3) · ×1
  • Duplicated block (11 lines × 3) apps/agent_web/src/mcp_server.erl:706 — apps/agent_web/src/mcp_server.erl:706-716 | apps/agent_web/src/mcp_server.erl:776-786 | apps/agent_web/src/mcp_server.erl:839-849 — 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.
D4 · Code Duplication · Duplicated block (10 lines × 7) · ×1
  • Duplicated block (10 lines × 7) apps/agent_web/src/workflow_api_handler.erl:112 — apps/agent_web/src/workflow_api_handler.erl:112-121 | apps/agent_web/src/workflow_api_handler.erl:157-166 | apps/agent_web/src/workflow_api_handler.erl:193-202 | apps/agent_web/src/workflow_api_handler.erl:240-249 | apps/agent_web/src/workflow_api_handler.erl:296-305 | apps/agent_web/src/workflow_api_handler.erl:351-360 | apps/agent_web/src/workflow_api_handler.erl:375-384 — all 7 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (8–10 lines × 4) · ×1
  • Duplicated block (8–10 lines × 4) apps/agent_web/src/agent_api_handler.erl:210 — apps/agent_web/src/agent_api_handler.erl:210-217 | apps/agent_web/src/agent_chat_handler.erl:47-55 | apps/agent_web/src/bulk_operations_handler.erl:14-23 | apps/agent_web/src/workflow_api_handler.erl:11-20 — before extracting anything, compare `apps/agent_web/src/bulk_operations_handler.erl` and `apps/agent_web/src/workflow_api_handler.erl` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (9 lines × 8) · ×1
  • Duplicated block (9 lines × 8) apps/agent_web/src/agent_api_handler.erl:239 — apps/agent_web/src/agent_api_handler.erl:239-247 | apps/agent_web/src/workflow_api_handler.erl:112-120 | apps/agent_web/src/workflow_api_handler.erl:157-165 | apps/agent_web/src/workflow_api_handler.erl:193-201 | apps/agent_web/src/workflow_api_handler.erl:240-248 | apps/agent_web/src/workflow_api_handler.erl:296-304 | apps/agent_web/src/workflow_api_handler.erl:351-359 | apps/agent_web/src/workflow_api_handler.erl:375-383 — there are 8 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 8 sites; resolving a subset leaves the remainder to drift apart.
D4 · Code Duplication · Duplicated block (8–9 lines × 4) · ×1
  • Duplicated block (8–9 lines × 4) apps/agent_web/src/mcp_sse_handler.erl:150 — apps/agent_web/src/mcp_sse_handler.erl:150-157 | apps/agent_web/src/mcp_sse_handler.erl:167-175 | apps/agent_web/src/mcp_sse_handler.erl:185-193 | apps/agent_web/src/mcp_sse_handler.erl:204-212 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (8–9 lines × 2) · ×1
  • Duplicated block (8–9 lines × 2) apps/agent_web/src/mcp_client_v2.erl:393 — apps/agent_web/src/mcp_client_v2.erl:393-400 | apps/agent_web/src/mcp_transport.erl:213-221 — before extracting anything, compare `apps/agent_web/src/mcp_client_v2.erl` and `apps/agent_web/src/mcp_transport.erl` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (8 lines × 7) · ×1
  • Duplicated block (8 lines × 7) apps/agent_web/src/consciousness_bridge_api_handler.erl:124 — apps/agent_web/src/consciousness_bridge_api_handler.erl:124-131 | apps/agent_web/src/consciousness_bridge_api_handler.erl:175-182 | apps/agent_web/src/consciousness_bridge_api_handler.erl:202-209 | apps/agent_web/src/consciousness_bridge_api_handler.erl:231-238 | apps/agent_web/src/neural_swarm_api_handler.erl:112-119 | apps/agent_web/src/neural_swarm_api_handler.erl:163-170 | apps/agent_web/src/neural_swarm_api_handler.erl:212-219 — before extracting anything, compare `apps/agent_web/src/consciousness_bridge_api_handler.erl` and `apps/agent_web/src/neural_swarm_api_handler.erl` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (8 lines × 5) · ×1
  • Duplicated block (8 lines × 5) apps/agent_web/src/agent_monitoring_handler.erl:40 — apps/agent_web/src/agent_monitoring_handler.erl:40-47 | apps/agent_web/src/knowledge_base_handler.erl:16-23 | apps/agent_web/src/knowledge_base_handler.erl:69-76 | apps/agent_web/src/knowledge_base_handler.erl:161-168 | apps/agent_web/src/knowledge_base_handler.erl:179-186 — there are 5 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 5 sites; resolving a subset leaves the remainder to drift apart.
D4 · Code Duplication · Duplicated block (7 lines × 11) · ×1
  • Duplicated block (7 lines × 11) apps/agent_web/src/examples_handler.erl:88 — apps/agent_web/src/examples_handler.erl:88-94 | apps/agent_web/src/examples_handler.erl:99-105 | apps/agent_web/src/examples_handler.erl:110-116 | apps/agent_web/src/examples_handler.erl:121-127 | apps/agent_web/src/examples_handler.erl:132-138 | apps/agent_web/src/examples_handler.erl:143-149 | apps/agent_web/src/examples_handler.erl:154-160 | apps/agent_web/src/examples_handler.erl:165-171 | apps/agent_web/src/examples_handler.erl:176-182 | apps/agent_web/src/examples_handler.erl:187-193 | apps/agent_web/src/examples_handler.erl:198-204 — all 11 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.
D4 · Code Duplication · Duplicated block (7 lines × 6) · ×1
  • Duplicated block (7 lines × 6) apps/agent_web/src/agent_monitoring_handler.erl:39 — apps/agent_web/src/agent_monitoring_handler.erl:39-45 | apps/agent_web/src/knowledge_base_handler.erl:15-21 | apps/agent_web/src/knowledge_base_handler.erl:44-50 | apps/agent_web/src/knowledge_base_handler.erl:68-74 | apps/agent_web/src/knowledge_base_handler.erl:160-166 | apps/agent_web/src/knowledge_base_handler.erl:178-184 — there are 6 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 6 sites; resolving a subset leaves the remainder to drift apart.
D4 · Code Duplication · Duplicated block (7 lines × 5) · ×1
  • Duplicated block (7 lines × 5) apps/agent_web/src/model_api_handler.erl:203 — apps/agent_web/src/model_api_handler.erl:203-209 | apps/agent_web/src/model_api_handler.erl:281-287 | apps/agent_web/src/model_api_handler.erl:335-341 | apps/agent_web/src/model_api_handler.erl:484-490 | apps/agent_web/src/model_api_handler.erl:529-535 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (6–7 lines × 2) · ×1
  • Duplicated block (6–7 lines × 2) apps/agent_web/src/mcp_advanced_config.erl:89 — apps/agent_web/src/mcp_advanced_config.erl:89-94 | apps/agent_web/src/mcp_advanced_config.erl:106-112 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (5–6 lines × 5) · ×1
  • Duplicated block (5–6 lines × 5) apps/agent_web/src/mcp_api_handler.erl:31 — apps/agent_web/src/mcp_api_handler.erl:31-35 | apps/agent_web/src/mcp_api_handler.erl:64-69 | apps/agent_web/src/mcp_api_handler.erl:80-84 | apps/agent_web/src/mcp_api_handler.erl:113-117 | apps/agent_web/src/mcp_api_handler.erl:167-171 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (6 lines × 3) · ×1
  • Duplicated block (6 lines × 3) apps/agent_web/src/agent_scheduling_handler.erl:404 — apps/agent_web/src/agent_scheduling_handler.erl:404-409 | apps/agents/src/agent_scheduler_engine.erl:352-357 | apps/agents/src/agent_temporal_awareness.erl:514-519 — 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.
D4 · Code Duplication · Duplicated block (5–6 lines × 2) · ×1
  • Duplicated block (5–6 lines × 2) apps/agent_web/src/quantum_performance_analyzer.erl:170 — apps/agent_web/src/quantum_performance_analyzer.erl:170-174 | apps/agent_web/src/quantum_performance_analyzer.erl:354-359 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (3–5 lines × 3) · ×1
  • Duplicated block (3–5 lines × 3) apps/agent_web/src/ai_error_interpreter.erl:101 — apps/agent_web/src/ai_error_interpreter.erl:101-105 | apps/agent_web/src/ai_timeout_analyzer.erl:143-147 | apps/agent_web/src/crash_report_processor.erl:120-122 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (35 lines × 2) · ×1
  • Duplicated block (35 lines × 2) apps/agents/src/quantum_consciousness_engine.erl:176 — apps/agents/src/quantum_consciousness_engine.erl:176-210 | apps/agents/src/temporal_meta_analyzer.erl:180-214 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (10 lines × 6) · ×1
  • Duplicated block (10 lines × 6) apps/agent_web/src/ai_error_interpreter.erl:169 — apps/agent_web/src/ai_error_interpreter.erl:169-178 | apps/agent_web/src/ai_error_interpreter.erl:207-216 | apps/agent_web/src/ai_timeout_analyzer.erl:266-275 | apps/agent_web/src/ai_timeout_analyzer.erl:502-511 | apps/agent_web/src/crash_ai_analyzer.erl:98-107 | apps/agent_web/src/crash_ai_analyzer.erl:167-176 — there are 6 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 6 sites; resolving a subset leaves the remainder to drift apart.
D4 · Code Duplication · Duplicated block (10 lines × 4) · ×1
  • Duplicated block (10 lines × 4) apps/agent_web/src/mcp_management_handler.erl:176 — apps/agent_web/src/mcp_management_handler.erl:176-185 | apps/agent_web/src/mcp_management_handler.erl:242-251 | apps/agent_web/src/mcp_management_handler.erl:279-288 | apps/agent_web/src/mcp_management_handler.erl:316-325 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (9 lines × 6) · ×1
  • Duplicated block (9 lines × 6) apps/agent_web/src/consciousness_bridge_api_handler.erl:156 — apps/agent_web/src/consciousness_bridge_api_handler.erl:156-164 | apps/agent_web/src/consciousness_bridge_api_handler.erl:183-191 | apps/agent_web/src/consciousness_bridge_api_handler.erl:210-218 | apps/agent_web/src/neural_swarm_api_handler.erl:143-151 | apps/agent_web/src/neural_swarm_api_handler.erl:171-179 | apps/agent_web/src/neural_swarm_api_handler.erl:194-202 — before extracting anything, compare `apps/agent_web/src/consciousness_bridge_api_handler.erl` and `apps/agent_web/src/neural_swarm_api_handler.erl` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (7 lines × 4) · ×1
  • Duplicated block (7 lines × 4) apps/agent_web/src/agent_monitoring_handler.erl:62 — apps/agent_web/src/agent_monitoring_handler.erl:62-68 | apps/agent_web/src/examples_handler.erl:15-21 | apps/agent_web/src/knowledge_base_handler.erl:125-131 | apps/agent_web/src/knowledge_base_handler.erl:147-153 — there are 4 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart.
D5 · Coupling · Off the main sequence · ×1
  • Off the main sequence: openai — openai: 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.
D6 · Cohesion (LCOM4) · Low cohesion · ×1
  • Low cohesion: hierarchical_task_executor (LCOM4 4) apps/agents/src/hierarchical_task_executor.erl:4 — hierarchical_task_executor's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
P1 · CI/CD gates · No CI pipeline · ×1
  • No CI pipeline — No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
R10 · Code Duplication · Duplicated block with local edits (35 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (35 matched lines × 2 locations) REDACTED:642 — REDACTED:642 · REDACTED:1499 — the two spans are one implementation copied and then locally edited — 157 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block with local edits (33 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (33 matched lines × 2 locations) apps/agent_web/frontend/src/components/AdvancedMessageRenderer.tsx:171 — apps/agent_web/frontend/src/components/AdvancedMessageRenderer.tsx:171 · apps/agent_web/frontend/src/components/AdvancedMessageRenderer.tsx:232 — the two spans are one implementation copied and then locally edited — 194 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (31 lines × 2 locations) · ×1
  • Duplicated block (31 lines × 2 locations) apps/agent_web/frontend/src/components/InteractiveReasoningControls.tsx:310 — apps/agent_web/frontend/src/components/InteractiveReasoningControls.tsx:310 · apps/agent_web/frontend/src/components/InteractiveReasoningControls.tsx:417 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication · Duplicated block (30 lines × 2 locations) · ×1
  • Duplicated block (30 lines × 2 locations) apps/agent_web/frontend/src/components/ComprehensiveMCPManager.tsx:453 — apps/agent_web/frontend/src/components/ComprehensiveMCPManager.tsx:453 · apps/agent_web/frontend/src/components/ComprehensiveMCPManager.tsx:541 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
R10 · Code Duplication · Duplicated block (28 lines × 2 locations) · ×1
  • Duplicated block (28 lines × 2 locations) apps/agent_web/frontend/src/components/ComprehensiveMCPManager.tsx:500 — apps/agent_web/frontend/src/components/ComprehensiveMCPManager.tsx:500 · apps/agent_web/frontend/src/components/ComprehensiveMCPManager.tsx:601 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication · Duplicated block (27 lines × 2 locations) · ×1
  • Duplicated block (27 lines × 2 locations) apps/agent_web/frontend/src/components/VirtualizedAgentList.tsx:98 — apps/agent_web/frontend/src/components/VirtualizedAgentList.tsx:98 · apps/agent_web/frontend/src/components/VirtualizedAgentList.tsx:146 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (21 lines × 2 locations) · ×1
  • Duplicated block (21 lines × 2 locations) apps/agent_web/frontend/src/components/ComprehensiveMCPManager.tsx:763 — apps/agent_web/frontend/src/components/ComprehensiveMCPManager.tsx:763 · apps/agent_web/frontend/src/components/ComprehensiveMCPManager.tsx:833 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (18 lines × 2 locations) · ×1
  • Duplicated block (18 lines × 2 locations) apps/agent_web/frontend/src/components/UltimatePerformanceDashboard.tsx:432 — apps/agent_web/frontend/src/components/UltimatePerformanceDashboard.tsx:432 · apps/agent_web/frontend/src/components/UltimatePerformanceDashboard.tsx:468 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
R10 · Code Duplication · Duplicated block (18 lines × 3 locations) · ×1
  • Duplicated block (18 lines × 3 locations) apps/agent_web/frontend/src/components/UltraAdvancedDashboard.tsx:621 — apps/agent_web/frontend/src/components/UltraAdvancedDashboard.tsx:621 · apps/agent_web/frontend/src/components/UltraAdvancedDashboard.tsx:645 · apps/agent_web/frontend/src/components/UltraAdvancedDashboard.tsx:669 — 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.
R10 · Code Duplication · Duplicated block with local edits (17 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (17 matched lines × 2 locations) apps/agent_web/frontend/src/components/CrashMonitorDashboard.tsx:220 — apps/agent_web/frontend/src/components/CrashMonitorDashboard.tsx:220 · apps/agent_web/frontend/src/components/MCPOrchestrationEngine.tsx:373 — the two spans are one implementation copied and then locally edited — 72 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 (15 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (15 matched lines × 2 locations) REDACTED:392 — REDACTED:392 · apps/agent_web/frontend/src/components/MCPServerManager.tsx:69 — the two spans are one implementation copied and then locally edited — 69 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (15 lines × 4 locations) · ×1
  • Duplicated block (15 lines × 4 locations) apps/agent_web/frontend/src/components/AdvancedStructuredOutputsManager.tsx:320 — apps/agent_web/frontend/src/components/AdvancedStructuredOutputsManager.tsx:320 · apps/agent_web/frontend/src/components/AdvancedStructuredOutputsManager.tsx:425 · apps/agent_web/frontend/src/components/AdvancedStructuredOutputsManager.tsx:493 · apps/agent_web/frontend/src/components/AdvancedStructuredOutputsManager.tsx:565 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
R10 · Code Duplication · Duplicated block with local edits (14 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (14 matched lines × 2 locations) apps/agent_web/frontend/src/components/ExamplesPanel.tsx:11 — apps/agent_web/frontend/src/components/ExamplesPanel.tsx:11 · REDACTED:711 — the two spans are one implementation copied and then locally edited — 82 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 (14 lines × 3 locations) · ×1
  • Duplicated block (14 lines × 3 locations) apps/agent_web/frontend/src/components/ModelConfiguration.tsx:311 — apps/agent_web/frontend/src/components/ModelConfiguration.tsx:311 · apps/agent_web/frontend/src/components/ModelConfiguration.tsx:325 · apps/agent_web/frontend/src/components/ModelConfiguration.tsx:340 — 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.
R10 · Code Duplication · Duplicated block (13 lines × 9 locations) · ×1
  • Duplicated block (13 lines × 9 locations) apps/agent_web/frontend/src/components/AdaptiveAIInterface.tsx:407 — apps/agent_web/frontend/src/components/AdaptiveAIInterface.tsx:407 · apps/agent_web/frontend/src/components/AdaptiveAIInterface.tsx:452 · apps/agent_web/frontend/src/components/AdaptiveAIInterface.tsx:497 · apps/agent_web/frontend/src/components/ApiKeyManager.tsx:336 · +5 more site(s) not listed — the 3 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R10 · Code Duplication · Duplicated block (13 lines × 4 locations) · ×1
  • Duplicated block (13 lines × 4 locations) apps/agent_web/frontend/src/components/QuantumConsciousnessInterface.tsx:396 — apps/agent_web/frontend/src/components/QuantumConsciousnessInterface.tsx:396 · apps/agent_web/frontend/src/components/QuantumConsciousnessInterface.tsx:466 · apps/agent_web/frontend/src/components/QuantumConsciousnessInterface.tsx:509 · apps/agent_web/frontend/src/components/QuantumConsciousnessInterface.tsx:568 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
R10 · Code Duplication · Duplicated block (12 lines × 4 locations) · ×1
  • Duplicated block (12 lines × 4 locations) REDACTED:938 — REDACTED:938 · REDACTED:951 · REDACTED:965 · REDACTED:979 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
R2 · Cyclomatic Complexity · Complex function SystemMonitoringDashboard (cyclomatic 25, cognitive 23) · ×1
  • Complex function SystemMonitoringDashboard (cyclomatic 25, cognitive 23) apps/agent_web/frontend/src/components/SystemMonitoringDashboard.tsx:65 — SystemMonitoringDashboard has cyclomatic complexity 25 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function ContentAnalysisBadge (cyclomatic 20, cognitive 13) · ×1
  • Complex function ContentAnalysisBadge (cyclomatic 20, cognitive 13) REDACTED:323 — ContentAnalysisBadge has cyclomatic complexity 20 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.
R2 · Cyclomatic Complexity · Complex function DiscoveryMeshDashboard (cyclomatic 18, cognitive 17) · ×1
  • Complex function DiscoveryMeshDashboard (cyclomatic 18, cognitive 17) apps/agent_web/frontend/src/components/DiscoveryMeshDashboard.tsx:55 — DiscoveryMeshDashboard 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.
R2 · Cyclomatic Complexity · Complex function analyzeContent (cyclomatic 18, cognitive 15) · ×1
  • Complex function analyzeContent (cyclomatic 18, cognitive 15) apps/agent_web/frontend/src/components/AdvancedMessageRenderer.tsx:43 — analyzeContent has cyclomatic complexity 18 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.
R2 · Cyclomatic Complexity · Complex function ErrorInterpretationPanel (cyclomatic 18, cognitive 15) · ×1
  • Complex function ErrorInterpretationPanel (cyclomatic 18, cognitive 15) apps/agent_web/frontend/src/components/ErrorInterpretationPanel.tsx:55 — ErrorInterpretationPanel has cyclomatic complexity 18 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.
R2 · Cyclomatic Complexity · Complex function Dashboard (cyclomatic 18, cognitive 14) · ×1
  • Complex function Dashboard (cyclomatic 18, cognitive 14) REDACTED:47 — Dashboard 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.
R2 · Cyclomatic Complexity · Complex function SimpleAdvancedChat (cyclomatic 17, cognitive 15) · ×1
  • Complex function SimpleAdvancedChat (cyclomatic 17, cognitive 15) REDACTED:384 — SimpleAdvancedChat 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.
R2 · Cyclomatic Complexity · Complex function CrashMonitorDashboard (cyclomatic 15, cognitive 14) · ×1
  • Complex function CrashMonitorDashboard (cyclomatic 15, cognitive 14) apps/agent_web/frontend/src/components/CrashMonitorDashboard.tsx:86 — CrashMonitorDashboard 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.
R2 · Cyclomatic Complexity · Complex function sendMessage (cyclomatic 15, cognitive 14) · ×1
  • Complex function sendMessage (cyclomatic 15, cognitive 14) REDACTED:792 — sendMessage 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.
R2 · Cyclomatic Complexity · Complex function DenseLayout (cyclomatic 13, cognitive 11) · ×1
  • Complex function DenseLayout (cyclomatic 13, cognitive 11) apps/agent_web/frontend/src/components/DenseLayout.tsx:14 — DenseLayout has cyclomatic complexity 13 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function InteractiveReasoningControls (cyclomatic 13, cognitive 11) · ×1
  • Complex function InteractiveReasoningControls (cyclomatic 13, cognitive 11) apps/agent_web/frontend/src/components/InteractiveReasoningControls.tsx:53 — InteractiveReasoningControls has cyclomatic complexity 13 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function ServerDetailPanel (cyclomatic 12, cognitive 11) · ×1
  • Complex function ServerDetailPanel (cyclomatic 12, cognitive 11) REDACTED:1222 — ServerDetailPanel has cyclomatic complexity 12 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function MCPServerManager (cyclomatic 12, cognitive 11) · ×1
  • Complex function MCPServerManager (cyclomatic 12, cognitive 11) apps/agent_web/frontend/src/components/MCPServerManager.tsx:23 — MCPServerManager has cyclomatic complexity 12 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function MultiAgentChat (cyclomatic 12, cognitive 11) · ×1
  • Complex function MultiAgentChat (cyclomatic 12, cognitive 11) apps/agent_web/frontend/src/components/MultiAgentChat.tsx:39 — MultiAgentChat has cyclomatic complexity 12 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function ChainOfThoughtVisualization (cyclomatic 12, cognitive 10) · ×1
  • Complex function ChainOfThoughtVisualization (cyclomatic 12, cognitive 10) apps/agent_web/frontend/src/components/ChainOfThoughtVisualization.tsx:52 — ChainOfThoughtVisualization has cyclomatic complexity 12 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.
R2 · Cyclomatic Complexity · Complex function handleWebSocketMessage (cyclomatic 12, cognitive 9) · ×1
  • Complex function handleWebSocketMessage (cyclomatic 12, cognitive 9) REDACTED:527 — handleWebSocketMessage has cyclomatic complexity 12 and cognitive complexity 9; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files · REDACTED · ×1
  • REDACTED: 1830 lines of code REDACTED:1 — REDACTED has 1830 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 · REDACTED · ×1
  • REDACTED: 1440 lines of code REDACTED:1 — REDACTED has 1440 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 · REDACTED · ×1
  • REDACTED: 1125 lines of code REDACTED:1 — REDACTED has 1125 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 · apps/agent_web/frontend/src/components/MCPOrchestrationEngine.tsx · ×1
  • apps/agent_web/frontend/src/components/MCPOrchestrationEngine.tsx: 1003 lines of code apps/agent_web/frontend/src/components/MCPOrchestrationEngine.tsx:1 — apps/agent_web/frontend/src/components/MCPOrchestrationEngine.tsx has 1003 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 · apps/agent_web/frontend/src/components/ComprehensiveMCPManager.tsx · ×1
  • apps/agent_web/frontend/src/components/ComprehensiveMCPManager.tsx: 992 lines of code apps/agent_web/frontend/src/components/ComprehensiveMCPManager.tsx:1 — apps/agent_web/frontend/src/components/ComprehensiveMCPManager.tsx has 992 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 · apps/agent_web/frontend/src/components/ModelTypeEditor.tsx · ×1
  • apps/agent_web/frontend/src/components/ModelTypeEditor.tsx: 850 lines of code apps/agent_web/frontend/src/components/ModelTypeEditor.tsx:1 — apps/agent_web/frontend/src/components/ModelTypeEditor.tsx has 850 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 · apps/agent_web/frontend/src/components/UltraAdvancedDashboard.tsx · ×1
  • apps/agent_web/frontend/src/components/UltraAdvancedDashboard.tsx: 844 lines of code apps/agent_web/frontend/src/components/UltraAdvancedDashboard.tsx:1 — apps/agent_web/frontend/src/components/UltraAdvancedDashboard.tsx has 844 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 · apps/agent_web/frontend/src/App.tsx · ×1
  • apps/agent_web/frontend/src/App.tsx: 673 lines of code apps/agent_web/frontend/src/App.tsx:1 — apps/agent_web/frontend/src/App.tsx has 673 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 · apps/agent_web/frontend/src/services/CollaborationManager.ts · ×1
  • apps/agent_web/frontend/src/services/CollaborationManager.ts: 644 lines of code apps/agent_web/frontend/src/services/CollaborationManager.ts:1 — apps/agent_web/frontend/src/services/CollaborationManager.ts has 644 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 · apps/agent_web/frontend/src/components/CrashMonitorDashboard.tsx · ×1
  • apps/agent_web/frontend/src/components/CrashMonitorDashboard.tsx: 636 lines of code apps/agent_web/frontend/src/components/CrashMonitorDashboard.tsx:1 — apps/agent_web/frontend/src/components/CrashMonitorDashboard.tsx has 636 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 · apps/agent_web/frontend/src/services/ChainOfThoughtEngine.ts · ×1
  • apps/agent_web/frontend/src/services/ChainOfThoughtEngine.ts: 619 lines of code apps/agent_web/frontend/src/services/ChainOfThoughtEngine.ts:1 — apps/agent_web/frontend/src/services/ChainOfThoughtEngine.ts has 619 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 · apps/agent_web/frontend/src/components/UltimatePerformanceDashboard.tsx · ×1
  • apps/agent_web/frontend/src/components/UltimatePerformanceDashboard.tsx: 589 lines of code apps/agent_web/frontend/src/components/UltimatePerformanceDashboard.tsx:1 — apps/agent_web/frontend/src/components/UltimatePerformanceDashboard.tsx has 589 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 · apps/agent_web/frontend/src/components/InteractiveWidgets.tsx · ×1
  • apps/agent_web/frontend/src/components/InteractiveWidgets.tsx: 572 lines of code apps/agent_web/frontend/src/components/InteractiveWidgets.tsx:1 — apps/agent_web/frontend/src/components/InteractiveWidgets.tsx has 572 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 · apps/agent_web/frontend/src/components/InteractiveReasoningControls.tsx · ×1
  • apps/agent_web/frontend/src/components/InteractiveReasoningControls.tsx: 569 lines of code apps/agent_web/frontend/src/components/InteractiveReasoningControls.tsx:1 — apps/agent_web/frontend/src/components/InteractiveReasoningControls.tsx has 569 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 · apps/agent_web/frontend/src/components/ModelConfiguration.tsx · ×1
  • apps/agent_web/frontend/src/components/ModelConfiguration.tsx: 569 lines of code apps/agent_web/frontend/src/components/ModelConfiguration.tsx:1 — apps/agent_web/frontend/src/components/ModelConfiguration.tsx has 569 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 · apps/agent_web/frontend/src/components/AdvancedStructuredOutputsManager.tsx · ×1
  • apps/agent_web/frontend/src/components/AdvancedStructuredOutputsManager.tsx: 562 lines of code apps/agent_web/frontend/src/components/AdvancedStructuredOutputsManager.tsx:1 — apps/agent_web/frontend/src/components/AdvancedStructuredOutputsManager.tsx has 562 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 · apps/agent_web/frontend/src/components/QuantumConsciousnessInterface.tsx · ×1
  • apps/agent_web/frontend/src/components/QuantumConsciousnessInterface.tsx: 562 lines of code apps/agent_web/frontend/src/components/QuantumConsciousnessInterface.tsx:1 — apps/agent_web/frontend/src/components/QuantumConsciousnessInterface.tsx has 562 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 · apps/agent_web/frontend/src/components/DiscoveryMeshDashboard.tsx · ×1
  • apps/agent_web/frontend/src/components/DiscoveryMeshDashboard.tsx: 558 lines of code apps/agent_web/frontend/src/components/DiscoveryMeshDashboard.tsx:1 — apps/agent_web/frontend/src/components/DiscoveryMeshDashboard.tsx has 558 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 · apps/agent_web/frontend/src/components/AdaptiveAIInterface.tsx · ×1
  • apps/agent_web/frontend/src/components/AdaptiveAIInterface.tsx: 542 lines of code apps/agent_web/frontend/src/components/AdaptiveAIInterface.tsx:1 — apps/agent_web/frontend/src/components/AdaptiveAIInterface.tsx has 542 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 · apps/agent_web/frontend/src/components/Timeline.tsx · ×1
  • apps/agent_web/frontend/src/components/Timeline.tsx: 542 lines of code apps/agent_web/frontend/src/components/Timeline.tsx:1 — apps/agent_web/frontend/src/components/Timeline.tsx has 542 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 · apps/agent_web/frontend/src/components/ToolRegistry.tsx · ×1
  • apps/agent_web/frontend/src/components/ToolRegistry.tsx: 526 lines of code apps/agent_web/frontend/src/components/ToolRegistry.tsx:1 — apps/agent_web/frontend/src/components/ToolRegistry.tsx has 526 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 · apps/agent_web/frontend/src/components/DynamicUIManager.tsx · ×1
  • apps/agent_web/frontend/src/components/DynamicUIManager.tsx: 503 lines of code apps/agent_web/frontend/src/components/DynamicUIManager.tsx:1 — apps/agent_web/frontend/src/components/DynamicUIManager.tsx has 503 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 · apps/agent_web/frontend/src/components/SystemMonitoringDashboard.tsx · ×1
  • apps/agent_web/frontend/src/components/SystemMonitoringDashboard.tsx: 502 lines of code apps/agent_web/frontend/src/components/SystemMonitoringDashboard.tsx:1 — apps/agent_web/frontend/src/components/SystemMonitoringDashboard.tsx has 502 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 · apps/agent_web/frontend/src/components/MultiAgentChat.tsx · ×1
  • apps/agent_web/frontend/src/components/MultiAgentChat.tsx: 499 lines of code apps/agent_web/frontend/src/components/MultiAgentChat.tsx:1 — apps/agent_web/frontend/src/components/MultiAgentChat.tsx has 499 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 · apps/agent_web/frontend/src/components/ChainOfThoughtVisualization.tsx · ×1
  • apps/agent_web/frontend/src/components/ChainOfThoughtVisualization.tsx: 489 lines of code apps/agent_web/frontend/src/components/ChainOfThoughtVisualization.tsx:1 — apps/agent_web/frontend/src/components/ChainOfThoughtVisualization.tsx has 489 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · apps/agent_web/frontend/src/components/ErrorInterpretationPanel.tsx · ×1
  • apps/agent_web/frontend/src/components/ErrorInterpretationPanel.tsx: 481 lines of code apps/agent_web/frontend/src/components/ErrorInterpretationPanel.tsx:1 — apps/agent_web/frontend/src/components/ErrorInterpretationPanel.tsx has 481 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 · apps/agent_web/frontend/src/services/ContextualRetrieval.ts · ×1
  • apps/agent_web/frontend/src/services/ContextualRetrieval.ts: 479 lines of code apps/agent_web/frontend/src/services/ContextualRetrieval.ts:1 — apps/agent_web/frontend/src/services/ContextualRetrieval.ts has 479 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 · apps/agent_web/frontend/src/components/OAuthManager.tsx · ×1
  • apps/agent_web/frontend/src/components/OAuthManager.tsx: 463 lines of code apps/agent_web/frontend/src/components/OAuthManager.tsx:1 — apps/agent_web/frontend/src/components/OAuthManager.tsx has 463 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 · apps/agent_web/frontend/src/components/FleetManagementDashboard.tsx · ×1
  • apps/agent_web/frontend/src/components/FleetManagementDashboard.tsx: 448 lines of code apps/agent_web/frontend/src/components/FleetManagementDashboard.tsx:1 — apps/agent_web/frontend/src/components/FleetManagementDashboard.tsx has 448 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · apps/agent_web/frontend/src/components/PipedreamConnectionManager.tsx · ×1
  • apps/agent_web/frontend/src/components/PipedreamConnectionManager.tsx: 430 lines of code apps/agent_web/frontend/src/components/PipedreamConnectionManager.tsx:1 — apps/agent_web/frontend/src/components/PipedreamConnectionManager.tsx has 430 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 · apps/agent_web/frontend/src/components/AdvancedMessageRenderer.tsx · ×1
  • apps/agent_web/frontend/src/components/AdvancedMessageRenderer.tsx: 407 lines of code apps/agent_web/frontend/src/components/AdvancedMessageRenderer.tsx:1 — apps/agent_web/frontend/src/components/AdvancedMessageRenderer.tsx has 407 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R4 · Test Coverage · Test Coverage · ×1
  • Test Coverage — 0% of 83 production file(s) reachable from 0 test file(s) via the import graph — 'production' here is the RESIDUE: every source file left once tests, tooling, generated output, config, declarations and declaration-only modules, fixture corpora, type fixtures, behaviour-free data modules, re-export barrels, registration/constant data modules and service workers are set aside, so the percentage is taken over a smaller denominator than the workspace's file count
R5 · Dependency Freshness · Dependency Freshness · ×1
  • Dependency Freshness — 34 outdated package(s); JS/npm CVEs scored in D30
R6 · Tooling · No lint script · ×1
  • No lint script — test ✓ · lint ✗ · typecheck ✓ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
R7 · Dead Code · Dead file (~1069 LoC) · ×1
  • Dead file (~1069 LoC) apps/agent_web/frontend/src/components/ComprehensiveMCPManager.tsx — no import path from any entry point (3 application, 3 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~923 LoC) · ×1
  • Dead file (~923 LoC) apps/agent_web/frontend/src/components/UltraAdvancedDashboard.tsx — no import path from any entry point (3 application, 3 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~896 LoC) · ×1
  • Dead file (~896 LoC) apps/agent_web/frontend/src/components/ModelTypeEditor.tsx — no import path from any entry point (3 application, 3 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~755 LoC) · ×1
  • Dead file (~755 LoC) apps/agent_web/frontend/src/services/CollaborationManager.ts — no import path from any entry point (3 application, 3 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~624 LoC) · ×1
  • Dead file (~624 LoC) apps/agent_web/frontend/src/components/QuantumConsciousnessInterface.tsx — no import path from any entry point (3 application, 3 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~623 LoC) · ×1
  • Dead file (~623 LoC) apps/agent_web/frontend/src/components/InteractiveWidgets.tsx — no import path from any entry point (3 application, 3 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~622 LoC) · ×1
  • Dead file (~622 LoC) apps/agent_web/frontend/src/components/UltimatePerformanceDashboard.tsx — no import path from any entry point (3 application, 3 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~571 LoC) · ×1
  • Dead file (~571 LoC) apps/agent_web/frontend/src/services/ContextualRetrieval.ts — no import path from any entry point (3 application, 3 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/agent_web/frontend/src/components/DynamicUIManager.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
R7 · Dead Code · Dead file (~562 LoC) · ×1
  • Dead file (~562 LoC) apps/agent_web/frontend/src/components/DynamicUIManager.tsx — no import path from any entry point (3 application, 3 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~555 LoC) · ×1
  • Dead file (~555 LoC) apps/agent_web/frontend/src/components/ToolRegistry.tsx — no import path from any entry point (3 application, 3 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~504 LoC) · ×1
  • Dead file (~504 LoC) apps/agent_web/frontend/src/components/OAuthManager.tsx — no import path from any entry point (3 application, 3 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~481 LoC) · ×1
  • Dead file (~481 LoC) apps/agent_web/frontend/src/components/FleetManagementDashboard.tsx — no import path from any entry point (3 application, 3 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~477 LoC) · ×1
  • Dead file (~477 LoC) apps/agent_web/frontend/src/components/AdvancedMessageRenderer.tsx — no import path from any entry point (3 application, 3 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/agent_web/frontend/src/components/DynamicUIManager.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
R7 · Dead Code · Dead file (~459 LoC) · ×1
  • Dead file (~459 LoC) apps/agent_web/frontend/src/components/PipedreamConnectionManager.tsx — no import path from any entry point (3 application, 3 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~404 LoC) · ×1
  • Dead file (~404 LoC) apps/agent_web/frontend/src/components/ClaudeCLI.tsx — no import path from any entry point (3 application, 3 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/agent_web/frontend/src/components/MainLayoutWithSidebar.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
R7 · Dead Code · Dead file (~329 LoC) · ×1
  • Dead file (~329 LoC) apps/agent_web/frontend/src/components/AgentQuorumPanel.tsx — no import path from any entry point (3 application, 3 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (REDACTED) — 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
R7 · Dead Code · Dead file (~311 LoC) · ×1
  • Dead file (~311 LoC) REDACTED — no import path from any entry point (3 application, 3 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~301 LoC) · ×1
  • Dead file (~301 LoC) apps/agent_web/frontend/src/components/AgentCommunicationPanel.tsx — no import path from any entry point (3 application, 3 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (REDACTED) — 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
R7 · Dead Code · Dead file (~299 LoC) · ×1
  • Dead file (~299 LoC) apps/agent_web/frontend/src/components/MCPOAuthManager.tsx — no import path from any entry point (3 application, 3 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/agent_web/frontend/src/components/ComprehensiveMCPManager.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
R7 · Dead Code · Dead file (~298 LoC) · ×1
  • Dead file (~298 LoC) apps/agent_web/frontend/src/components/MainLayoutWithSidebar.tsx — no import path from any entry point (3 application, 3 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~294 LoC) · ×1
  • Dead file (~294 LoC) apps/agent_web/frontend/src/components/MCPServerManager.tsx — no import path from any entry point (3 application, 3 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~155 LoC) · ×1
  • Dead file (~155 LoC) apps/agent_web/frontend/src/components/DenseDashboard.tsx — no import path from any entry point (3 application, 3 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R8 · Dependency Hygiene · Unused dependency '@headlessui/react' · ×1
  • Unused dependency '@headlessui/react' — Declared in apps/agent_web/frontend/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency '@radix-ui/react-alert-dialog' · ×1
  • Unused dependency '@radix-ui/react-alert-dialog' — Declared in apps/agent_web/frontend/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency '@radix-ui/react-dropdown-menu' · ×1
  • Unused dependency '@radix-ui/react-dropdown-menu' — Declared in apps/agent_web/frontend/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
S1 · Web-Security Posture · Third-party script without Subresource Integrity · ×1
  • Third-party script without Subresource Integrity REDACTED:7 — `https://unpkg.com/react@18/umd/react.production.min.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. 6 such include(s) across the repository's markup.
X1 · Async correctness · `async` callback passed to `forEach` · ×1
  • `async` callback passed to `forEach` apps/agent_web/frontend/src/components/MultiAgentChat.tsx:387 — `forEach` ignores what its callback returns, so the Promise each `async` call returns is dropped: nothing can await it, the code after this loop runs before any of the awaited work has finished (a function that `await`s around this loop still returns early), and a rejection is never handled — in Node.js an unhandled rejection terminates the process by default, and in a browser it is lost. Iterate with `for (const item of items) { await … }` when the work must run in order, or `await Promise.all(items.map(async (item) => { … }))` when it may run concurrently, so the enclosing function finishes only when the work does and its failures reach the caller. Where firing and forgetting is genuinely intended, make the callback's whole body a `try { … } catch (e) { … }` that handles the failure, so it cannot escape.
Minor — 24 finding(s)
X10 · Duplicated predicate · Duplicated predicate · ×5
  • Duplicated predicate apps/agents/src/agent_scheduler_engine.erl:362 — `M1 =:= M2 andalso S1 =:= S2 andalso U1 < U2` appears character-identically in 2 files — apps/agents/src/agent_scheduler_engine.erl, apps/agents/src/agent_temporal_awareness.erl. 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 apps/agents/src/agent_temporal_awareness.erl:509 — `M1 =:= M2 andalso S1 =:= S2 andalso U1 > U2` appears character-identically in 2 files — apps/agents/src/agent_temporal_awareness.erl, apps/agents/src/timeline_event_store.erl. 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 apps/agent_web/frontend/src/components/AgentCommunicationPanel.tsx:106 — `agent?.name || agent?.type || id.substring(0, 8)` appears character-identically in 3 files — apps/agent_web/frontend/src/components/AgentCommunicationPanel.tsx, apps/agent_web/frontend/src/components/AgentQuorumPanel.tsx, apps/agent_web/frontend/src/components/MultiAgentChat.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 apps/agent_web/frontend/src/App.tsx:95 — `e.key === 'k' && (e.metaKey || e.ctrlKey)` appears character-identically in 2 files — apps/agent_web/frontend/src/App.tsx, apps/agent_web/frontend/src/components/CommandPalette.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 apps/agent_web/frontend/src/services/ContextualRetrieval.ts:182 — `this.ws && this.ws.readyState === WebSocket.OPEN` appears character-identically in 2 files — apps/agent_web/frontend/src/services/ContextualRetrieval.ts, 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.
X31 · Test-only surface in a production module · Test-only surface in a production module · ×3
  • Test-only surface in a production module apps/agents/test_basic_agent.erl:3 — `test_basic_agent:test_basic_functionality/0` is exported unconditionally and its name carries a test marker at a name-segment boundary, so the shipped module publishes a function named for the test tree. No other module in this repository calls it at any arity. Erlang has no visibility below `-export`, so this is part of the module's public contract: it cannot be changed without a compatibility argument. Nothing tells the next maintainer that its only caller is a test. Wrapping the attribute in `-ifdef(TEST). … -endif.` keeps the test's access and removes it from the shipped module.
  • Test-only surface in a production module simple_test.erl:5 — `simple_test:test/0` is exported unconditionally and its name IS the test marker, so the shipped module publishes a function named for the test tree. No other module in this repository calls it at any arity. Erlang has no visibility below `-export`, so this is part of the module's public contract: it cannot be changed without a compatibility argument. Nothing tells the next maintainer that its only caller is a test. Wrapping the attribute in `-ifdef(TEST). … -endif.` keeps the test's access and removes it from the shipped module.
  • Test-only surface in a production module simple_weather_test.erl:2 — `simple_weather_test:test/0` is exported unconditionally and its name IS the test marker, so the shipped module publishes a function named for the test tree. No other module in this repository calls it at any arity. Erlang has no visibility below `-export`, so this is part of the module's public contract: it cannot be changed without a compatibility argument. Nothing tells the next maintainer that its only caller is a test. Wrapping the attribute in `-ifdef(TEST). … -endif.` keeps the test's access and removes it from the shipped module.
D30 · Dependency Vulnerabilities · Low CVE · ×2
  • REDACTED
  • REDACTED
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion — 2 of 6 project(s) overshoot their size bounds, lowering Project Cohesion to 3.3/10. The most over is `apps/agents` (61388 LoC, 126 module-visible types across 2 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
P2 · Observability · Logging is not universal · ×1
  • Logging is not universal — Only 1/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `sandbox/myapp`.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST — No static application security testing detected. For this repository's stack, add dialyzer or elvis — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
P3 · Security & performance tooling · No dependency-update automation · ×1
  • No dependency-update automation apps/agent_web/frontend/package.json:11 — `apps/agent_web/frontend/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
P6 · Release Hygiene · No changelog · ×1
  • No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
R7 · Dead Code · Unused export 'sanitizeCss' · ×1
  • Unused export 'sanitizeCss' apps/agent_web/frontend/src/utils/sanitize.ts:90 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'escapeHtml' · ×1
  • Unused export 'escapeHtml' apps/agent_web/frontend/src/utils/sanitize.ts:102 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused private field 'collaborationCallbacks' · ×1
  • Unused private field 'collaborationCallbacks' apps/agent_web/frontend/src/services/ChainOfThoughtEngine.ts:77 — Nothing in its class reads or assigns this private field (for a constructor parameter property: it is stored and never read), and no string key or test reaches it by name. Remove it, or use it where it was meant to take effect.
X2 · Cancellation propagation · Not all async functions that make a request accept an AbortSignal · ×1
  • Not all async functions that make a request accept an AbortSignal — Only 1/54 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
X5 · Nullable reference types · Strict null checking is not enabled everywhere the repository type-checks · ×1
  • Strict null checking is not enabled everywhere the repository type-checks — 0/2 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.
X5 · Nullable reference types · Null assertions (`!`) reduce the strict null checking score · ×1
  • Null assertions (`!`) reduce the strict null checking score — ~0.3 `!` null assertions per 1k TypeScript source lines — 9 assertion(s) across the 29134 source line(s) of the 82 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: apps/agent_web/frontend/src/services/CollaborationManager.ts (4), apps/agent_web/frontend/src/components/MCPOrchestrationEngine.tsx (1), REDACTED (1). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
Minor — 15 finding(s)
D12 · Dependency Hygiene · Outdated · ×15
  • Outdated: accept — `accept` is declared `"0.3.5"` in rebar.config and pinned there by the committed REDACTED, but 0.3.7 is the current stable release on hex.pm — so this repository is behind by the version it names itself. rebar3 resolves an exact requirement to that exact release, so the remedy is to raise the declaration in rebar.config and re-run `rebar3 upgrade accept`, committing the updated REDACTED.
  • Outdated: base64url — `base64url` is declared `"0.0.1"` in rebar.config and pinned there by the committed REDACTED, but 1.0.1 is the current stable release on hex.pm — so this repository is behind by the version it names itself. This crosses a major version. rebar3 resolves an exact requirement to that exact release, so the remedy is to raise the declaration in rebar.config and re-run `rebar3 upgrade base64url`, committing the updated REDACTED.
  • Outdated: cowboy — `cowboy` is declared `"2.10.0"` in rebar.config and pinned there by the committed REDACTED, but 2.20.0 is the current stable release on hex.pm — so this repository is behind by the version it names itself. rebar3 resolves an exact requirement to that exact release, so the remedy is to raise the declaration in rebar.config and re-run `rebar3 upgrade cowboy`, committing the updated REDACTED.
  • Outdated: exometer_core — `exometer_core` is declared `"1.6.2"` in rebar.config and pinned there by the committed REDACTED, but 2.0.0 is the current stable release on hex.pm — so this repository is behind by the version it names itself. This crosses a major version. rebar3 resolves an exact requirement to that exact release, so the remedy is to raise the declaration in rebar.config and re-run `rebar3 upgrade exometer_core`, committing the updated REDACTED.
  • Outdated: folsom — `folsom` is declared `"1.0.0"` in rebar.config and pinned there by the committed REDACTED, but 1.1.0 is the current stable release on hex.pm — so this repository is behind by the version it names itself. rebar3 resolves an exact requirement to that exact release, so the remedy is to raise the declaration in rebar.config and re-run `rebar3 upgrade folsom`, committing the updated REDACTED.
  • Outdated: gproc — `gproc` is declared `"0.9.0"` in rebar.config and pinned there by the committed REDACTED, but 1.3.0 is the current stable release on hex.pm — so this repository is behind by the version it names itself. This crosses a major version. rebar3 resolves an exact requirement to that exact release, so the remedy is to raise the declaration in rebar.config and re-run `rebar3 upgrade gproc`, committing the updated REDACTED.
  • Outdated: gun — `gun` is declared `"2.0.1"` in rebar.config and pinned there by the committed REDACTED, but 2.7.0 is the current stable release on hex.pm — so this repository is behind by the version it names itself. rebar3 resolves an exact requirement to that exact release, so the remedy is to raise the declaration in rebar.config and re-run `rebar3 upgrade gun`, committing the updated REDACTED.
  • Outdated: hackney — `hackney` is declared `"1.18.1"` in rebar.config and pinned there by the committed REDACTED, but 4.9.1 is the current stable release on hex.pm — so this repository is behind by the version it names itself. This crosses a major version. rebar3 resolves an exact requirement to that exact release, so the remedy is to raise the declaration in rebar.config and re-run `rebar3 upgrade hackney`, committing the updated REDACTED.
  • Outdated: jiffy — `jiffy` is declared `"1.1.2"` in rebar.config and pinned there by the committed REDACTED, but 2.0.2 is the current stable release on hex.pm — so this repository is behind by the version it names itself. This crosses a major version. rebar3 resolves an exact requirement to that exact release, so the remedy is to raise the declaration in rebar.config and re-run `rebar3 upgrade jiffy`, committing the updated REDACTED.
  • Outdated: observer_cli — `observer_cli` is declared `"1.7.4"` in rebar.config and pinned there by the committed REDACTED, but 2.0.0 is the current stable release on hex.pm — so this repository is behind by the version it names itself. This crosses a major version. rebar3 resolves an exact requirement to that exact release, so the remedy is to raise the declaration in rebar.config and re-run `rebar3 upgrade observer_cli`, committing the updated REDACTED.
  • Outdated: prometheus — `prometheus` is declared `"4.8.0"` in rebar.config and pinned there by the committed REDACTED, but 6.1.3 is the current stable release on hex.pm — so this repository is behind by the version it names itself. This crosses a major version. rebar3 resolves an exact requirement to that exact release, so the remedy is to raise the declaration in rebar.config and re-run `rebar3 upgrade prometheus`, committing the updated REDACTED.
  • Outdated: prometheus_cowboy — `prometheus_cowboy` is declared `"0.1.8"` in rebar.config and pinned there by the committed REDACTED, but 0.2.0 is the current stable release on hex.pm — so this repository is behind by the version it names itself. rebar3 resolves an exact requirement to that exact release, so the remedy is to raise the declaration in rebar.config and re-run `rebar3 upgrade prometheus_cowboy`, committing the updated REDACTED.
  • Outdated: prometheus_httpd — `prometheus_httpd` is declared `"2.1.11"` in rebar.config and pinned there by the committed REDACTED, but 2.1.15 is the current stable release on hex.pm — so this repository is behind by the version it names itself. rebar3 resolves an exact requirement to that exact release, so the remedy is to raise the declaration in rebar.config and re-run `rebar3 upgrade prometheus_httpd`, committing the updated REDACTED.
  • Outdated: quantile_estimator — `quantile_estimator` is declared `"0.2.1"` in rebar.config and pinned there by the committed REDACTED, but 1.0.2 is the current stable release on hex.pm — so this repository is behind by the version it names itself. This crosses a major version. rebar3 resolves an exact requirement to that exact release, so the remedy is to raise the declaration in rebar.config and re-run `rebar3 upgrade quantile_estimator`, committing the updated REDACTED.
  • Outdated: uuid_erl — `uuid_erl` is declared `"2.0.6"` in rebar.config and pinned there by the committed REDACTED, but 2.0.7 is the current stable release on hex.pm — so this repository is behind by the version it names itself. rebar3 resolves an exact requirement to that exact release, so the remedy is to raise the declaration in rebar.config and re-run `rebar3 upgrade uuid_erl`, committing the updated REDACTED.

Appendix B — Reproduction & audit trail

Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-ac7cd44fa9f04c7297e00c4d2521e365/history.json --exit-code 0 --source .3artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-ac7cd44fa9f04c7297e00c4d2521e365/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt .7artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update21artifacts/raw/trivy-fs.json
D31 · IaC & Container Securitytrivy—trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.0—
D32 · Data Compliance (PII/GDPR)semgrep—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.0—
D36 · Supply-chain Provenance & Signingprovenance—provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.0—
D37 · Vulnerability-disclosure Policydisclosure—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.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update0artifacts/raw/trivy-fs.json

Run 01a18cce-7bd4-705a-833b-a31275c67da4 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

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.

⬇ Findings, MITRE CWE-tagged .sarif⬇ Health changelog .md