Public report of whiteducksoftware/flock, published 22 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 reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). Watchdog 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, 22 October 2026, 22:44 UTC · Survey ID cd_4733e4b52a0742da84680504b4054786
whiteducksoftware/flock
Measured 22 October 2026, 22:27 UTC, at code version 7515e51
CAI scoreAt riskUp 1 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 74,459 lines of product code in 2 projects, tests not counted · Estimated rebuild effort: about 1.0 person-years · Weakest lens: Security and Compliance, 55
Findings by how serious they are
55 critical478 serious100 minor
11 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
22 October 2026, 22:27 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.
A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.
The score is deterministic, which means the same code always gets the same score. 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 ▸
81of 88 dimensions measured by tools. The other 7 are advisory notes from an AI model, which explain the code but don't count towards the score.
607of 633 findings point to an exact file and line, so you can open each one in the code. The other 26 concern the repository as a whole, such as missing documentation.
88dimensions across 7 lenses, read from 74,459 lines of product code in 2 projects.
whiteducksoftware/flock scores 57 out of 100, but it is rated At risk while a critical security finding is open; the score itself is unchanged. The project hasn't declared a stable release yet, so its lenses are rated against a lower bar than a released product's, while the score itself is worked out as for any repository.
The weakest lens counts most in the score, and here that is Security and Compliance, which scores 55 and is rated Adequate. Its Supply-chain Provenance & Signing dimension scores 0 out of 10, and until that reaches 4, Security and Compliance can't be rated higher than Adequate. The first actions are to resolve the 2 Leaked secret finding(s) in REDACTED Scanning and to enforce authorization at every handler — a guard on each route, or a global authentication guard/middleware with explicit public opt-outs, so protected-by-default is demonstrable. The weakest lenses score close to each other, so improving any of them moves the score.
55 findings are critical: 18 in Keyboard semantics, 14 in Static Analysis (SAST), 11 in Forms & labels, six in Dependency Vulnerabilities, two in Circular Imports, two in REDACTED Scanning and two in Secrets (history).
Watchdog couldn't measure 11 dimensions in this code, among them Code Coverage, Navigability and Data Protection, so they are left out of the score. The product code is 74,459 lines, which would take an estimated 1.0 person-years, around €150,000, to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
The weakest lenses score close to each other, so improving any of them moves the score.
Code composition: what the lines of code are
Product code 51%Tests 49%
New since the last survey: 139 findings
These 139 critical or serious findings weren't in the previous survey, on 8 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
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: 147 findings
These 147 critical or serious findings were in the previous survey, on 8 October 2026, and are gone from this one. The first 100 are listed here.
€50,000 to €250,000, for 839 to 2,661 hours of work, about 1.0 person-years for 1 to 2 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.8 at a score of 57. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 74,459 lines of product code
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 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED.
Enforce authorization at every handler — a guard on each route, or a global authentication guard/middleware with explicit public opt-outs, so protected-by-default is demonstrable.
Raises the score by about 2 points · Medium effort · Access Controls
3
Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED.
Raises the score by about 0.7 points · Low effort · Secrets (history)
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 €150,000 to build again, about 1.0 person-years of work. Its weakest lens is Security and Compliance, at 55 (Adequate). Security and Compliance is about how well the product is protected, and how it handles personal data. Because the weakest lens counts most in the score, work on Security and Compliance also moves the score most.
Based on: the rebuild estimate · the Security and Compliance grade · how much each lens counts
What to do: Start with the Security and Compliance actions in Top priorities.
If you do one thing first · First action
Resolve the 2 Leaked secret finding(s) in REDACTED Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 2 points for low effort, because it clears the 2 REDACTED Scanning findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 7.1 out of 10. Code at that level is slower to change than clean code, and Watchdog estimates the extra work at 2% to 5% on every change. The history of the code shows how much it changes: about 57,891 lines over the last 90 days, which is about 234,780 lines a year. At that pace, the extra work comes to an estimated 13.7 to 81.9 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of Watchdog's own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture: 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.
349 modules, with 257 dependencies between them. One loop runs through 6 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 309 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.
src.flock.application.types uses src.flock.core.artifacts, so a change to src.flock.core.artifacts can break src.flock.application.types, while a change to src.flock.application.types can't break src.flock.core.artifacts.
Position
Below the diagonal: src.flock.application.types uses a module listed above it, which is the healthy direction.
src.flock.components.agent.base uses src.flock.core.artifacts, so a change to src.flock.core.artifacts can break src.flock.components.agent.base, while a change to src.flock.components.agent.base can't break src.flock.core.artifacts.
Position
Below the diagonal: src.flock.components.agent.base uses a module listed above it, which is the healthy direction.
src.flock.components.agent.base uses src.flock.utils.runtime, so a change to src.flock.utils.runtime can break src.flock.components.agent.base, while a change to src.flock.components.agent.base can't break src.flock.utils.runtime.
Position
Below the diagonal: src.flock.components.agent.base uses a module listed above it, which is the healthy direction.
src.flock.core.store uses src.flock.core.artifacts, so a change to src.flock.core.artifacts can break src.flock.core.store, while a change to src.flock.core.store can't break src.flock.core.artifacts.
Position
Below the diagonal: src.flock.core.store uses a module listed above it, which is the healthy direction.
src.flock.core.subscription uses src.flock.core.artifacts, so a change to src.flock.core.artifacts can break src.flock.core.subscription, while a change to src.flock.core.subscription can't break src.flock.core.artifacts.
Position
Below the diagonal: src.flock.core.subscription uses a module listed above it, which is the healthy direction.
12→29 src.flock.core.subscription uses src.flock.core.orchestratorpart of a loop✕
Connections
1 pair of types, where a type in src.flock.core.subscription uses a type in src.flock.core.orchestrator.
src.flock.core.subscription uses src.flock.core.orchestrator, so a change to src.flock.core.orchestrator can break src.flock.core.subscription, while a change to src.flock.core.subscription can't break src.flock.core.orchestrator.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
src.flock.frontend.src.components.modules.ModuleRegistry uses src.flock.frontend.src.types.graph, so a change to src.flock.frontend.src.types.graph can break src.flock.frontend.src.components.modules.ModuleRegistry, while a change to src.flock.frontend.src.components.modules.ModuleRegistry can't break src.flock.frontend.src.types.graph.
Position
Below the diagonal: src.flock.frontend.src.components.modules.ModuleRegistry uses a module listed above it, which is the healthy direction.
src.flock.frontend.src.services uses src.flock.frontend.src.types.graph, so a change to src.flock.frontend.src.types.graph can break src.flock.frontend.src.services, while a change to src.flock.frontend.src.services can't break src.flock.frontend.src.types.graph.
Position
Below the diagonal: src.flock.frontend.src.services uses a module listed above it, which is the healthy direction.
src.flock.mcp.config uses src.flock.mcp.types.types, so a change to src.flock.mcp.types.types can break src.flock.mcp.config, while a change to src.flock.mcp.config can't break src.flock.mcp.types.types.
Position
Below the diagonal: src.flock.mcp.config uses a module listed above it, which is the healthy direction.
src.flock.api.collector uses src.flock.utils.runtime, so a change to src.flock.utils.runtime can break src.flock.api.collector, while a change to src.flock.api.collector can't break src.flock.utils.runtime.
Position
Below the diagonal: src.flock.api.collector uses a module listed above it, which is the healthy direction.
src.flock.api.collector uses src.flock.components.agent.base, so a change to src.flock.components.agent.base can break src.flock.api.collector, while a change to src.flock.api.collector can't break src.flock.components.agent.base.
Position
Below the diagonal: src.flock.api.collector uses a module listed above it, which is the healthy direction.
src.flock.api.collector uses src.flock.core.store, so a change to src.flock.core.store can break src.flock.api.collector, while a change to src.flock.api.collector can't break src.flock.core.store.
Position
Below the diagonal: src.flock.api.collector uses a module listed above it, which is the healthy direction.
src.flock.components.server.artifacts.artifacts_component uses src.flock.components.server.base, so a change to src.flock.components.server.base can break src.flock.components.server.artifacts.artifacts_component, while a change to src.flock.components.server.artifacts.artifacts_component can't break src.flock.components.server.base.
Position
Below the diagonal: src.flock.components.server.artifacts.artifacts_component uses a module listed above it, which is the healthy direction.
src.flock.components.server.artifacts.artifacts_component uses src.flock.core.artifacts, so a change to src.flock.core.artifacts can break src.flock.components.server.artifacts.artifacts_component, while a change to src.flock.components.server.artifacts.artifacts_component can't break src.flock.core.artifacts.
Position
Below the diagonal: src.flock.components.server.artifacts.artifacts_component uses a module listed above it, which is the healthy direction.
src.flock.components.server.artifacts.artifacts_component uses src.flock.core.visibility, so a change to src.flock.core.visibility can break src.flock.components.server.artifacts.artifacts_component, while a change to src.flock.components.server.artifacts.artifacts_component can't break src.flock.core.visibility.
Position
Below the diagonal: src.flock.components.server.artifacts.artifacts_component uses a module listed above it, which is the healthy direction.
src.flock.components.server.artifacts.artifacts_component uses src.flock.core.store, so a change to src.flock.core.store can break src.flock.components.server.artifacts.artifacts_component, while a change to src.flock.components.server.artifacts.artifacts_component can't break src.flock.core.store.
Position
Below the diagonal: src.flock.components.server.artifacts.artifacts_component uses a module listed above it, which is the healthy direction.
src.flock.core.agent uses src.flock.core.artifacts, so a change to src.flock.core.artifacts can break src.flock.core.agent, while a change to src.flock.core.agent can't break src.flock.core.artifacts.
Position
Below the diagonal: src.flock.core.agent uses a module listed above it, which is the healthy direction.
src.flock.core.agent uses src.flock.core.visibility, so a change to src.flock.core.visibility can break src.flock.core.agent, while a change to src.flock.core.agent can't break src.flock.core.visibility.
Position
Below the diagonal: src.flock.core.agent uses a module listed above it, which is the healthy direction.
src.flock.core.agent uses src.flock.utils.runtime, so a change to src.flock.utils.runtime can break src.flock.core.agent, while a change to src.flock.core.agent can't break src.flock.utils.runtime.
Position
Below the diagonal: src.flock.core.agent uses a module listed above it, which is the healthy direction.
src.flock.core.agent uses src.flock.components.agent.base, so a change to src.flock.components.agent.base can break src.flock.core.agent, while a change to src.flock.core.agent can't break src.flock.components.agent.base.
Position
Below the diagonal: src.flock.core.agent uses a module listed above it, which is the healthy direction.
18→29 src.flock.core.agent uses src.flock.core.orchestratorpart of a loop✕
Connections
2 pairs of types, where a type in src.flock.core.agent uses a type in src.flock.core.orchestrator.
src.flock.core.agent uses src.flock.core.orchestrator, so a change to src.flock.core.orchestrator can break src.flock.core.agent, while a change to src.flock.core.agent can't break src.flock.core.orchestrator.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
src.flock.decisions.coverage uses src.flock.core.artifacts, so a change to src.flock.core.artifacts can break src.flock.decisions.coverage, while a change to src.flock.decisions.coverage can't break src.flock.core.artifacts.
Position
Below the diagonal: src.flock.decisions.coverage uses a module listed above it, which is the healthy direction.
src.flock.decisions.coverage uses src.flock.core.visibility, so a change to src.flock.core.visibility can break src.flock.decisions.coverage, while a change to src.flock.decisions.coverage can't break src.flock.core.visibility.
Position
Below the diagonal: src.flock.decisions.coverage uses a module listed above it, which is the healthy direction.
src.flock.decisions.coverage uses src.flock.utils.runtime, so a change to src.flock.utils.runtime can break src.flock.decisions.coverage, while a change to src.flock.decisions.coverage can't break src.flock.utils.runtime.
Position
Below the diagonal: src.flock.decisions.coverage uses a module listed above it, which is the healthy direction.
src.flock.decisions.coverage uses src.flock.components.agent.base, so a change to src.flock.components.agent.base can break src.flock.decisions.coverage, while a change to src.flock.decisions.coverage can't break src.flock.components.agent.base.
Position
Below the diagonal: src.flock.decisions.coverage uses a module listed above it, which is the healthy direction.
src.flock.engines.dspy_engine uses src.flock.core.artifacts, so a change to src.flock.core.artifacts can break src.flock.engines.dspy_engine, while a change to src.flock.engines.dspy_engine can't break src.flock.core.artifacts.
Position
Below the diagonal: src.flock.engines.dspy_engine uses a module listed above it, which is the healthy direction.
src.flock.engines.dspy_engine uses src.flock.utils.runtime, so a change to src.flock.utils.runtime can break src.flock.engines.dspy_engine, while a change to src.flock.engines.dspy_engine can't break src.flock.utils.runtime.
Position
Below the diagonal: src.flock.engines.dspy_engine uses a module listed above it, which is the healthy direction.
src.flock.engines.dspy_engine uses src.flock.components.agent.base, so a change to src.flock.components.agent.base can break src.flock.engines.dspy_engine, while a change to src.flock.engines.dspy_engine can't break src.flock.components.agent.base.
Position
Below the diagonal: src.flock.engines.dspy_engine uses a module listed above it, which is the healthy direction.
src.flock.mcp.client uses src.flock.mcp.types.types, so a change to src.flock.mcp.types.types can break src.flock.mcp.client, while a change to src.flock.mcp.client can't break src.flock.mcp.types.types.
Position
Below the diagonal: src.flock.mcp.client uses a module listed above it, which is the healthy direction.
src.flock.mcp.client uses src.flock.mcp.config, so a change to src.flock.mcp.config can break src.flock.mcp.client, while a change to src.flock.mcp.client can't break src.flock.mcp.config.
Position
Below the diagonal: src.flock.mcp.client uses a module listed above it, which is the healthy direction.
src.flock.orchestrator.batch_accumulator uses src.flock.core.artifacts, so a change to src.flock.core.artifacts can break src.flock.orchestrator.batch_accumulator, while a change to src.flock.orchestrator.batch_accumulator can't break src.flock.core.artifacts.
Position
Below the diagonal: src.flock.orchestrator.batch_accumulator uses a module listed above it, which is the healthy direction.
src.flock.orchestrator.batch_accumulator uses src.flock.core.subscription, so a change to src.flock.core.subscription can break src.flock.orchestrator.batch_accumulator, while a change to src.flock.orchestrator.batch_accumulator can't break src.flock.core.subscription.
Position
Below the diagonal: src.flock.orchestrator.batch_accumulator uses a module listed above it, which is the healthy direction.
src.flock.orchestrator.correlation_engine uses src.flock.core.artifacts, so a change to src.flock.core.artifacts can break src.flock.orchestrator.correlation_engine, while a change to src.flock.orchestrator.correlation_engine can't break src.flock.core.artifacts.
Position
Below the diagonal: src.flock.orchestrator.correlation_engine uses a module listed above it, which is the healthy direction.
src.flock.orchestrator.correlation_engine uses src.flock.core.subscription, so a change to src.flock.core.subscription can break src.flock.orchestrator.correlation_engine, while a change to src.flock.orchestrator.correlation_engine can't break src.flock.core.subscription.
Position
Below the diagonal: src.flock.orchestrator.correlation_engine uses a module listed above it, which is the healthy direction.
src.flock.components.orchestrator.base uses src.flock.core.artifacts, so a change to src.flock.core.artifacts can break src.flock.components.orchestrator.base, while a change to src.flock.components.orchestrator.base can't break src.flock.core.artifacts.
Position
Below the diagonal: src.flock.components.orchestrator.base uses a module listed above it, which is the healthy direction.
src.flock.components.orchestrator.base uses src.flock.core.subscription, so a change to src.flock.core.subscription can break src.flock.components.orchestrator.base, while a change to src.flock.components.orchestrator.base can't break src.flock.core.subscription.
Position
Below the diagonal: src.flock.components.orchestrator.base uses a module listed above it, which is the healthy direction.
src.flock.components.orchestrator.base uses src.flock.core.agent, so a change to src.flock.core.agent can break src.flock.components.orchestrator.base, while a change to src.flock.components.orchestrator.base can't break src.flock.core.agent.
Position
Below the diagonal: src.flock.components.orchestrator.base uses a module listed above it, which is the healthy direction.
24→29 src.flock.components.orchestrator.base uses src.flock.core.orchestratorpart of a loop✕
Connections
1 pair of types, where a type in src.flock.components.orchestrator.base uses a type in src.flock.core.orchestrator.
src.flock.components.orchestrator.base uses src.flock.core.orchestrator, so a change to src.flock.core.orchestrator can break src.flock.components.orchestrator.base, while a change to src.flock.components.orchestrator.base can't break src.flock.core.orchestrator.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
src.flock.decisions.engine uses src.flock.utils.runtime, so a change to src.flock.utils.runtime can break src.flock.decisions.engine, while a change to src.flock.decisions.engine can't break src.flock.utils.runtime.
Position
Below the diagonal: src.flock.decisions.engine uses a module listed above it, which is the healthy direction.
src.flock.decisions.engine uses src.flock.components.agent.base, so a change to src.flock.components.agent.base can break src.flock.decisions.engine, while a change to src.flock.decisions.engine can't break src.flock.components.agent.base.
Position
Below the diagonal: src.flock.decisions.engine uses a module listed above it, which is the healthy direction.
src.flock.decisions.engine uses src.flock.core.agent, so a change to src.flock.core.agent can break src.flock.decisions.engine, while a change to src.flock.decisions.engine can't break src.flock.core.agent.
Position
Below the diagonal: src.flock.decisions.engine uses a module listed above it, which is the healthy direction.
src.flock.decisions.explain uses src.flock.core.visibility, so a change to src.flock.core.visibility can break src.flock.decisions.explain, while a change to src.flock.decisions.explain can't break src.flock.core.visibility.
Position
Below the diagonal: src.flock.decisions.explain uses a module listed above it, which is the healthy direction.
src.flock.decisions.explain uses src.flock.utils.runtime, so a change to src.flock.utils.runtime can break src.flock.decisions.explain, while a change to src.flock.decisions.explain can't break src.flock.utils.runtime.
Position
Below the diagonal: src.flock.decisions.explain uses a module listed above it, which is the healthy direction.
src.flock.decisions.explain uses src.flock.engines.dspy_engine, so a change to src.flock.engines.dspy_engine can break src.flock.decisions.explain, while a change to src.flock.decisions.explain can't break src.flock.engines.dspy_engine.
Position
Below the diagonal: src.flock.decisions.explain uses a module listed above it, which is the healthy direction.
src.flock.orchestrator.component_runner uses src.flock.core.artifacts, so a change to src.flock.core.artifacts can break src.flock.orchestrator.component_runner, while a change to src.flock.orchestrator.component_runner can't break src.flock.core.artifacts.
Position
Below the diagonal: src.flock.orchestrator.component_runner uses a module listed above it, which is the healthy direction.
src.flock.orchestrator.component_runner uses src.flock.core.subscription, so a change to src.flock.core.subscription can break src.flock.orchestrator.component_runner, while a change to src.flock.orchestrator.component_runner can't break src.flock.core.subscription.
Position
Below the diagonal: src.flock.orchestrator.component_runner uses a module listed above it, which is the healthy direction.
src.flock.orchestrator.component_runner uses src.flock.core.agent, so a change to src.flock.core.agent can break src.flock.orchestrator.component_runner, while a change to src.flock.orchestrator.component_runner can't break src.flock.core.agent.
Position
Below the diagonal: src.flock.orchestrator.component_runner uses a module listed above it, which is the healthy direction.
src.flock.orchestrator.event_emitter uses src.flock.core.artifacts, so a change to src.flock.core.artifacts can break src.flock.orchestrator.event_emitter, while a change to src.flock.orchestrator.event_emitter can't break src.flock.core.artifacts.
Position
Below the diagonal: src.flock.orchestrator.event_emitter uses a module listed above it, which is the healthy direction.
src.flock.orchestrator.event_emitter uses src.flock.core.subscription, so a change to src.flock.core.subscription can break src.flock.orchestrator.event_emitter, while a change to src.flock.orchestrator.event_emitter can't break src.flock.core.subscription.
Position
Below the diagonal: src.flock.orchestrator.event_emitter uses a module listed above it, which is the healthy direction.
src.flock.orchestrator.event_emitter uses src.flock.orchestrator.batch_accumulator, so a change to src.flock.orchestrator.batch_accumulator can break src.flock.orchestrator.event_emitter, while a change to src.flock.orchestrator.event_emitter can't break src.flock.orchestrator.batch_accumulator.
Position
Below the diagonal: src.flock.orchestrator.event_emitter uses a module listed above it, which is the healthy direction.
src.flock.orchestrator.event_emitter uses src.flock.orchestrator.correlation_engine, so a change to src.flock.orchestrator.correlation_engine can break src.flock.orchestrator.event_emitter, while a change to src.flock.orchestrator.event_emitter can't break src.flock.orchestrator.correlation_engine.
Position
Below the diagonal: src.flock.orchestrator.event_emitter uses a module listed above it, which is the healthy direction.
src.flock.core.orchestrator uses src.flock.components.server.base, so a change to src.flock.components.server.base can break src.flock.core.orchestrator, while a change to src.flock.core.orchestrator can't break src.flock.components.server.base.
Position
Below the diagonal: src.flock.core.orchestrator uses a module listed above it, which is the healthy direction.
src.flock.core.orchestrator uses src.flock.core.artifacts, so a change to src.flock.core.artifacts can break src.flock.core.orchestrator, while a change to src.flock.core.orchestrator can't break src.flock.core.artifacts.
Position
Below the diagonal: src.flock.core.orchestrator uses a module listed above it, which is the healthy direction.
src.flock.core.orchestrator uses src.flock.mcp.types.types, so a change to src.flock.mcp.types.types can break src.flock.core.orchestrator, while a change to src.flock.core.orchestrator can't break src.flock.mcp.types.types.
Position
Below the diagonal: src.flock.core.orchestrator uses a module listed above it, which is the healthy direction.
src.flock.core.orchestrator uses src.flock.core.subscription, so a change to src.flock.core.subscription can break src.flock.core.orchestrator, while a change to src.flock.core.orchestrator can't break src.flock.core.subscription.
Position
Below the diagonal: src.flock.core.orchestrator uses a module listed above it, which is the healthy direction.
src.flock.core.orchestrator uses src.flock.core.agent, so a change to src.flock.core.agent can break src.flock.core.orchestrator, while a change to src.flock.core.orchestrator can't break src.flock.core.agent.
Position
Below the diagonal: src.flock.core.orchestrator uses a module listed above it, which is the healthy direction.
src.flock.core.orchestrator uses src.flock.components.orchestrator.base, so a change to src.flock.components.orchestrator.base can break src.flock.core.orchestrator, while a change to src.flock.core.orchestrator can't break src.flock.components.orchestrator.base.
Position
Below the diagonal: src.flock.core.orchestrator uses a module listed above it, which is the healthy direction.
src.flock.api.graph_builder uses src.flock.core.store, so a change to src.flock.core.store can break src.flock.api.graph_builder, while a change to src.flock.api.graph_builder can't break src.flock.core.store.
Position
Below the diagonal: src.flock.api.graph_builder uses a module listed above it, which is the healthy direction.
src.flock.api.graph_builder uses src.flock.api.collector, so a change to src.flock.api.collector can break src.flock.api.graph_builder, while a change to src.flock.api.graph_builder can't break src.flock.api.collector.
Position
Below the diagonal: src.flock.api.graph_builder uses a module listed above it, which is the healthy direction.
src.flock.api.graph_builder uses src.flock.core.orchestrator, so a change to src.flock.core.orchestrator can break src.flock.api.graph_builder, while a change to src.flock.api.graph_builder can't break src.flock.core.orchestrator.
Position
Below the diagonal: src.flock.api.graph_builder uses a module listed above it, which is the healthy direction.
src.flock.components.orchestrator.activation uses src.flock.core.artifacts, so a change to src.flock.core.artifacts can break src.flock.components.orchestrator.activation, while a change to src.flock.components.orchestrator.activation can't break src.flock.core.artifacts.
Position
Below the diagonal: src.flock.components.orchestrator.activation uses a module listed above it, which is the healthy direction.
src.flock.components.orchestrator.activation uses src.flock.core.agent, so a change to src.flock.core.agent can break src.flock.components.orchestrator.activation, while a change to src.flock.components.orchestrator.activation can't break src.flock.core.agent.
Position
Below the diagonal: src.flock.components.orchestrator.activation uses a module listed above it, which is the healthy direction.
src.flock.components.orchestrator.activation uses src.flock.components.orchestrator.base, so a change to src.flock.components.orchestrator.base can break src.flock.components.orchestrator.activation, while a change to src.flock.components.orchestrator.activation can't break src.flock.components.orchestrator.base.
Position
Below the diagonal: src.flock.components.orchestrator.activation uses a module listed above it, which is the healthy direction.
src.flock.components.orchestrator.activation uses src.flock.core.orchestrator, so a change to src.flock.core.orchestrator can break src.flock.components.orchestrator.activation, while a change to src.flock.components.orchestrator.activation can't break src.flock.core.orchestrator.
Position
Below the diagonal: src.flock.components.orchestrator.activation uses a module listed above it, which is the healthy direction.
src.flock.components.orchestrator.circuit_breaker uses src.flock.core.artifacts, so a change to src.flock.core.artifacts can break src.flock.components.orchestrator.circuit_breaker, while a change to src.flock.components.orchestrator.circuit_breaker can't break src.flock.core.artifacts.
Position
Below the diagonal: src.flock.components.orchestrator.circuit_breaker uses a module listed above it, which is the healthy direction.
src.flock.components.orchestrator.circuit_breaker uses src.flock.core.subscription, so a change to src.flock.core.subscription can break src.flock.components.orchestrator.circuit_breaker, while a change to src.flock.components.orchestrator.circuit_breaker can't break src.flock.core.subscription.
Position
Below the diagonal: src.flock.components.orchestrator.circuit_breaker uses a module listed above it, which is the healthy direction.
src.flock.components.orchestrator.circuit_breaker uses src.flock.core.agent, so a change to src.flock.core.agent can break src.flock.components.orchestrator.circuit_breaker, while a change to src.flock.components.orchestrator.circuit_breaker can't break src.flock.core.agent.
Position
Below the diagonal: src.flock.components.orchestrator.circuit_breaker uses a module listed above it, which is the healthy direction.
src.flock.components.orchestrator.circuit_breaker uses src.flock.components.orchestrator.base, so a change to src.flock.components.orchestrator.base can break src.flock.components.orchestrator.circuit_breaker, while a change to src.flock.components.orchestrator.circuit_breaker can't break src.flock.components.orchestrator.base.
Position
Below the diagonal: src.flock.components.orchestrator.circuit_breaker uses a module listed above it, which is the healthy direction.
src.flock.components.orchestrator.circuit_breaker uses src.flock.core.orchestrator, so a change to src.flock.core.orchestrator can break src.flock.components.orchestrator.circuit_breaker, while a change to src.flock.components.orchestrator.circuit_breaker can't break src.flock.core.orchestrator.
Position
Below the diagonal: src.flock.components.orchestrator.circuit_breaker uses a module listed above it, which is the healthy direction.
src.flock.components.orchestrator.collection uses src.flock.core.artifacts, so a change to src.flock.core.artifacts can break src.flock.components.orchestrator.collection, while a change to src.flock.components.orchestrator.collection can't break src.flock.core.artifacts.
Position
Below the diagonal: src.flock.components.orchestrator.collection uses a module listed above it, which is the healthy direction.
src.flock.components.orchestrator.collection uses src.flock.core.subscription, so a change to src.flock.core.subscription can break src.flock.components.orchestrator.collection, while a change to src.flock.components.orchestrator.collection can't break src.flock.core.subscription.
Position
Below the diagonal: src.flock.components.orchestrator.collection uses a module listed above it, which is the healthy direction.
src.flock.components.orchestrator.collection uses src.flock.core.agent, so a change to src.flock.core.agent can break src.flock.components.orchestrator.collection, while a change to src.flock.components.orchestrator.collection can't break src.flock.core.agent.
Position
Below the diagonal: src.flock.components.orchestrator.collection uses a module listed above it, which is the healthy direction.
src.flock.components.orchestrator.collection uses src.flock.components.orchestrator.base, so a change to src.flock.components.orchestrator.base can break src.flock.components.orchestrator.collection, while a change to src.flock.components.orchestrator.collection can't break src.flock.components.orchestrator.base.
Position
Below the diagonal: src.flock.components.orchestrator.collection uses a module listed above it, which is the healthy direction.
src.flock.components.orchestrator.collection uses src.flock.core.orchestrator, so a change to src.flock.core.orchestrator can break src.flock.components.orchestrator.collection, while a change to src.flock.components.orchestrator.collection can't break src.flock.core.orchestrator.
Position
Below the diagonal: src.flock.components.orchestrator.collection uses a module listed above it, which is the healthy direction.
src.flock.components.orchestrator.deduplication uses src.flock.core.artifacts, so a change to src.flock.core.artifacts can break src.flock.components.orchestrator.deduplication, while a change to src.flock.components.orchestrator.deduplication can't break src.flock.core.artifacts.
Position
Below the diagonal: src.flock.components.orchestrator.deduplication uses a module listed above it, which is the healthy direction.
src.flock.components.orchestrator.deduplication uses src.flock.core.subscription, so a change to src.flock.core.subscription can break src.flock.components.orchestrator.deduplication, while a change to src.flock.components.orchestrator.deduplication can't break src.flock.core.subscription.
Position
Below the diagonal: src.flock.components.orchestrator.deduplication uses a module listed above it, which is the healthy direction.
src.flock.components.orchestrator.deduplication uses src.flock.core.agent, so a change to src.flock.core.agent can break src.flock.components.orchestrator.deduplication, while a change to src.flock.components.orchestrator.deduplication can't break src.flock.core.agent.
Position
Below the diagonal: src.flock.components.orchestrator.deduplication uses a module listed above it, which is the healthy direction.
src.flock.components.orchestrator.deduplication uses src.flock.components.orchestrator.base, so a change to src.flock.components.orchestrator.base can break src.flock.components.orchestrator.deduplication, while a change to src.flock.components.orchestrator.deduplication can't break src.flock.components.orchestrator.base.
Position
Below the diagonal: src.flock.components.orchestrator.deduplication uses a module listed above it, which is the healthy direction.
src.flock.components.orchestrator.deduplication uses src.flock.core.orchestrator, so a change to src.flock.core.orchestrator can break src.flock.components.orchestrator.deduplication, while a change to src.flock.components.orchestrator.deduplication can't break src.flock.core.orchestrator.
Position
Below the diagonal: src.flock.components.orchestrator.deduplication uses a module listed above it, which is the healthy direction.
src.flock.components.orchestrator.webhook uses src.flock.core.artifacts, so a change to src.flock.core.artifacts can break src.flock.components.orchestrator.webhook, while a change to src.flock.components.orchestrator.webhook can't break src.flock.core.artifacts.
Position
Below the diagonal: src.flock.components.orchestrator.webhook uses a module listed above it, which is the healthy direction.
src.flock.components.orchestrator.webhook uses src.flock.components.orchestrator.base, so a change to src.flock.components.orchestrator.base can break src.flock.components.orchestrator.webhook, while a change to src.flock.components.orchestrator.webhook can't break src.flock.components.orchestrator.base.
Position
Below the diagonal: src.flock.components.orchestrator.webhook uses a module listed above it, which is the healthy direction.
src.flock.components.orchestrator.webhook uses src.flock.core.orchestrator, so a change to src.flock.core.orchestrator can break src.flock.components.orchestrator.webhook, while a change to src.flock.components.orchestrator.webhook can't break src.flock.core.orchestrator.
Position
Below the diagonal: src.flock.components.orchestrator.webhook uses a module listed above it, which is the healthy direction.
src.flock.core uses src.flock.core.visibility, so a change to src.flock.core.visibility can break src.flock.core, while a change to src.flock.core can't break src.flock.core.visibility.
Position
Below the diagonal: src.flock.core uses a module listed above it, which is the healthy direction.
src.flock.core uses src.flock.core.store, so a change to src.flock.core.store can break src.flock.core, while a change to src.flock.core can't break src.flock.core.store.
Position
Below the diagonal: src.flock.core uses a module listed above it, which is the healthy direction.
src.flock.core uses src.flock.core.orchestrator, so a change to src.flock.core.orchestrator can break src.flock.core, while a change to src.flock.core can't break src.flock.core.orchestrator.
Position
Below the diagonal: src.flock.core uses a module listed above it, which is the healthy direction.
src.flock.decisions uses src.flock.core.artifacts, so a change to src.flock.core.artifacts can break src.flock.decisions, while a change to src.flock.decisions can't break src.flock.core.artifacts.
Position
Below the diagonal: src.flock.decisions uses a module listed above it, which is the healthy direction.
src.flock.decisions uses src.flock.core.visibility, so a change to src.flock.core.visibility can break src.flock.decisions, while a change to src.flock.decisions can't break src.flock.core.visibility.
Position
Below the diagonal: src.flock.decisions uses a module listed above it, which is the healthy direction.
src.flock.decisions uses src.flock.core.store, so a change to src.flock.core.store can break src.flock.decisions, while a change to src.flock.decisions can't break src.flock.core.store.
Position
Below the diagonal: src.flock.decisions uses a module listed above it, which is the healthy direction.
src.flock.decisions uses src.flock.core.agent, so a change to src.flock.core.agent can break src.flock.decisions, while a change to src.flock.decisions can't break src.flock.core.agent.
Position
Below the diagonal: src.flock.decisions uses a module listed above it, which is the healthy direction.
src.flock.decisions uses src.flock.decisions.engine, so a change to src.flock.decisions.engine can break src.flock.decisions, while a change to src.flock.decisions can't break src.flock.decisions.engine.
Position
Below the diagonal: src.flock.decisions uses a module listed above it, which is the healthy direction.
src.flock.decisions uses src.flock.decisions.explain, so a change to src.flock.decisions.explain can break src.flock.decisions, while a change to src.flock.decisions can't break src.flock.decisions.explain.
Position
Below the diagonal: src.flock.decisions uses a module listed above it, which is the healthy direction.
src.flock.decisions uses src.flock.core.orchestrator, so a change to src.flock.core.orchestrator can break src.flock.decisions, while a change to src.flock.decisions can't break src.flock.core.orchestrator.
Position
Below the diagonal: src.flock.decisions uses a module listed above it, which is the healthy direction.
src.flock.orchestrator.scheduler uses src.flock.core.artifacts, so a change to src.flock.core.artifacts can break src.flock.orchestrator.scheduler, while a change to src.flock.orchestrator.scheduler can't break src.flock.core.artifacts.
Position
Below the diagonal: src.flock.orchestrator.scheduler uses a module listed above it, which is the healthy direction.
src.flock.orchestrator.scheduler uses src.flock.core.visibility, so a change to src.flock.core.visibility can break src.flock.orchestrator.scheduler, while a change to src.flock.orchestrator.scheduler can't break src.flock.core.visibility.
Position
Below the diagonal: src.flock.orchestrator.scheduler uses a module listed above it, which is the healthy direction.
src.flock.orchestrator.scheduler uses src.flock.orchestrator.component_runner, so a change to src.flock.orchestrator.component_runner can break src.flock.orchestrator.scheduler, while a change to src.flock.orchestrator.scheduler can't break src.flock.orchestrator.component_runner.
Position
Below the diagonal: src.flock.orchestrator.scheduler uses a module listed above it, which is the healthy direction.
src.flock.orchestrator.scheduler uses src.flock.core.orchestrator, so a change to src.flock.core.orchestrator can break src.flock.orchestrator.scheduler, while a change to src.flock.orchestrator.scheduler can't break src.flock.core.orchestrator.
Position
Below the diagonal: src.flock.orchestrator.scheduler uses a module listed above it, which is the healthy direction.
src.flock.application.application uses src.flock.core.artifacts, so a change to src.flock.core.artifacts can break src.flock.application.application, while a change to src.flock.application.application can't break src.flock.core.artifacts.
Position
Below the diagonal: src.flock.application.application uses a module listed above it, which is the healthy direction.
src.flock.application.application uses src.flock.application.types, so a change to src.flock.application.types can break src.flock.application.application, while a change to src.flock.application.application can't break src.flock.application.types.
Position
Below the diagonal: src.flock.application.application uses a module listed above it, which is the healthy direction.
src.flock.application.application uses src.flock.core.orchestrator, so a change to src.flock.core.orchestrator can break src.flock.application.application, while a change to src.flock.application.application can't break src.flock.core.orchestrator.
Position
Below the diagonal: src.flock.application.application uses a module listed above it, which is the healthy direction.
src.flock.application.application uses src.flock.orchestrator.scheduler, so a change to src.flock.orchestrator.scheduler can break src.flock.application.application, while a change to src.flock.application.application can't break src.flock.orchestrator.scheduler.
Position
Below the diagonal: src.flock.application.application uses a module listed above it, which is the healthy direction.
src.flock.orchestrator.artifact_manager uses src.flock.core.artifacts, so a change to src.flock.core.artifacts can break src.flock.orchestrator.artifact_manager, while a change to src.flock.orchestrator.artifact_manager can't break src.flock.core.artifacts.
Position
Below the diagonal: src.flock.orchestrator.artifact_manager uses a module listed above it, which is the healthy direction.
src.flock.orchestrator.artifact_manager uses src.flock.core.store, so a change to src.flock.core.store can break src.flock.orchestrator.artifact_manager, while a change to src.flock.orchestrator.artifact_manager can't break src.flock.core.store.
Position
Below the diagonal: src.flock.orchestrator.artifact_manager uses a module listed above it, which is the healthy direction.
src.flock.orchestrator.artifact_manager uses src.flock.core.orchestrator, so a change to src.flock.core.orchestrator can break src.flock.orchestrator.artifact_manager, while a change to src.flock.orchestrator.artifact_manager can't break src.flock.core.orchestrator.
Position
Below the diagonal: src.flock.orchestrator.artifact_manager uses a module listed above it, which is the healthy direction.
src.flock.orchestrator.artifact_manager uses src.flock.orchestrator.scheduler, so a change to src.flock.orchestrator.scheduler can break src.flock.orchestrator.artifact_manager, while a change to src.flock.orchestrator.artifact_manager can't break src.flock.orchestrator.scheduler.
Position
Below the diagonal: src.flock.orchestrator.artifact_manager uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 60% · Adequate · gated by D2 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A03:2025 — Software Supply Chain Failures
19
High / Critical
A05:2025 — Injection
16
High / Critical
A07:2025 — Authentication Failures
5
High / Critical
Roadmap
Immediately resolve the two leaked secrets in REDACTED and REDACTED, then enforce a protected-by-default authorization model using global middleware with explicit public opt-outs. Reconcile the documentation to eliminate drift and ensure the README accurately reflects the current project structure and dependencies. Integrate a SAST step into CI to fail the build on security regressions, and finally, improve keyboard accessibility by making custom controls operable and fixing anchor links.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED.
Enforce authorization at every handler — a guard on each route, or a global authentication guard/middleware with explicit public opt-outs, so protected-by-default is demonstrable.
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 — 55
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 — 478
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 — 100
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 11
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
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. 81 of 88 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 7 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 1.0 — 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 — 88 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 607 of 633 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — 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: this repository's production source spans .ts, .tsx, .py, and our analyzer cannot run the .py test suite(s) — so no coverage was collected for the repository as a whole. The JavaScript/TypeScript half did build and run, and its own line coverage came back at 50.4% — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — coverage is excluded from the score rather than counted as a near-zero. In the meantime, produce a coverage report in a standard format (lcov — `vitest --coverage`, `jest --coverage`, `bun test --coverage --coverage-reporter=lcov`, or `nyc`, or `coverage run -m pytest` then `coverage xml`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures and real coverage will be read. You can widen what we reach: optional: produce a coverage report in a standard format (`coverage run -m pytest` then `coverage xml`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then both halves are read on the next scan.
D10 Test 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. The 438 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 225 test source file(s) (.py) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (11 contributor(s) across 2072 commit(s) sampled, automation and bot accounts excluded). One of them holds 84% of the history; the other 10 hold 1.6% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
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.
D32 Data Compliance (PII/GDPR) — 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. `src/flock/core/artifacts.py` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
AX1 Captive dependencies — 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 Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository defines its own container in src/flock/registry.py, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
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 DockerCompose (examples/12-dapr/inmemory/docker-compose.yml). compose up failed (exit 18 — an image could not be pulled) — scheduler Pulling flock-dapr Pulling placement Pulling flock-dapr Error Get "https://registry-1.docker.io/v2/": Forbidden scheduler Error Get "https://registry-1.docker.io/v2/": Forbidden placement Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: placement Pulling flock-dapr Pulling scheduler Pulling placement Error Get "https://registry-1.docker.io/v2/": Forbidden flock-dapr Error Get "https://registry-1.docker.io/v2/": Forbidden scheduler Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped.
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.
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. 'duckdb' is imported (src/flock/components/server/traces/trace_component.py:10), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
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. 'duckdb' is imported (src/flock/components/server/traces/trace_component.py:10), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
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. 'duckdb' is imported (src/flock/components/server/traces/trace_component.py:10), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
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 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 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. 19 further occurrence(s) are not listed individually; the score already reflects all 59.
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. 27 further occurrence(s) are not listed individually; the score already reflects all 67.
S1 Web-Security Posture — 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 web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
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.
D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
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 is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
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.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D22 Internal API Consistency: API-surface coherence is an LLM judgement over a sample of the public surface — consistency of intent across the whole API is approximated, not exhaustively verified.
D25 ADR Conformance: ADR conformance is the LLM-scored fraction of sampled code that follows recorded decisions — it checks the decisions that were written down and the slices it sampled, not unrecorded rules or the whole tree.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
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.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
The LLM boundary
LLM-set scores this run (7): D19, D20, D21, D22, D25, D26, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.
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.
+ 52 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 12 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with AgentBuilder.decides (cyclomatic 66), AgentNode.AgentNode (cyclomatic 65), LogicOperationsDisplay.LogicOperationsDisplay (cyclomatic 55). — 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 12 together lifts Cyclomatic Complexity from 5.9 to about 7.0/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 91 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 6 bodies over 60 down to 60 or less in Cognitive Complexity — start with TraceModuleJaeger.TraceModuleJaeger (cognitive 124), AgentBuilder.decides (cognitive 98), GraphAssembler._build_agent_nodes (cognitive 94). — 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 6 together lifts Cognitive Complexity from 3.0 to about 4.7/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes7.5 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 23 FunctionTooLong finding(s) in God Classes — start with TraceModuleJaeger.tsx, GraphCanvas.tsx, PublishControl.tsx. — One of this dimension's main actionable groups (23 warning-level).
Resolve the 17 FileTooLong finding(s) in God Classes — start with engine.py (2), TraceModuleJaeger.tsx, DecisionDisplay.tsx. — One of this dimension's main actionable groups (17 warning-level).
Resolve the 5 ClassTooLong finding(s) in God Classes — start with TraceModuleJaeger.tsx, GraphCanvas.tsx, PublishControl.tsx. — One of this dimension's main actionable groups (5 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
77 duplicated block group(s) detected. One further row reports members as variants of one another; it aggregates block groups already counted above and is not itself counted. 32 of the 78 are in trees this repository does not ship — vendored, example/demo, 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. Measured on part of this repository only: .tsx (16% of production source) was not exposed to THIS dimension's token comparison and is not in this count; duplication there is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream.
+ 51 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 8 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with guard.py, store.py, graph_builder.py. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 5 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with signature_builder.py (2), streaming_executor.py, flock_sse_server.py. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 5 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with agents_component.py, providers.py, 10_explain.py. — One of this dimension's main actionable groups (5 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
2 production modules (npm+Python), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with orchestrator.py. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the code respects its intended layering / architecture rules.
Method: Enforcement rung (Prevented/Verified/Documented) per checkable ADR via Roslyn, plus dependency cycles via the engine shared with D5/AX3. Deterministic, exact.
All 1 mechanizable ADR(s) are enforced: 0 by analyzers, 1 by tests. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).
What to do
Enforce Architectural Integrity in CI to reach Prevented (currently Verified). — Hardens enforcement from Verified toward Prevented — provenance only; does not change the score.
Detailed fixes: d7_recommendation.md.
Do you agree with this assessment?
D9 · Test Distribution9.9 / 10Exemplary✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
3559 test methods: 3376 unit, 143 integration, 0 BDD, 40 e2e. The JavaScript/TypeScript suite contributes 438 `it`/`test` case(s) across 33 test file(s) declaring at least one; its tier split is read from package names and paths only. The Python suite contributes 3121 test function(s) across 210 file(s) declaring at least one — every `def test…` in a file pytest or unittest would collect, which is those frameworks' own definition of a case; a parametrize table counts once, so this is a floor. Its tier split is read from file names and paths only.
✓ On the Gold path — maintain.
Detailed fixes: d9_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality10.0 / 10Stronggated by 1 serious finding✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
1 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 438 tests. Measured on the JavaScript/TypeScript suite only — at least 225 test source file(s) (.py) went unread, so its test quality is unmeasured and is not in these counts.
Skipped test: should emit warning when storage quota exceededsrc/flock/frontend/src/services/indexeddb.test.ts:632
Mock-dominated test: should pass filters from filterStore to backend · ×2src/flock/frontend/src/store/graphStore.test.ts:127
What to do
Resolve the 2 Mock-dominated test finding(s) in Test Quality — start with graphStore.test.ts (2). — One of this dimension's main actionable groups (2 recommendation-level).
Resolve the 1 Skipped test finding(s) in Test Quality — start with indexeddb.test.ts. — One of this dimension's main actionable groups (1 warning-level).
Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests pass reliably, with no flakiness.
Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.
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.
5 outdated, 0 yanked pinned Python distributions. Only EXACT pins are graded for currency: a floor or a range already installs the newest release it admits, so reporting one would report this repository for being current. Whether a deliberate upper cap has itself gone stale is a different and weaker question, and is not asked. Whether any distribution is UNMAINTAINED is not graded — PyPI publishes no maintenance status, and release age does not stand in for one. Lockfiles are not read (poetry.lock, REDACTED, Pipfile.lock, pdm.lock), so a lock-resolved install is outside this verdict. Known CVEs in this dependency graph are D30's question.
Outdated: aiosqlite · ×5
✓ On the Gold path — maintain.
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 76 shipped Python distribution(s) use a banned license. Licences were resolved from PyPI over the distributions a consumer installs — this repository's 6 declared runtime requirement(s) closed transitively over each distribution's published `requires_dist` (70 reached that way). Requirements it states ONLY under an extra, a PEP 735 dependency group, a Poetry dev group or a dev-named requirements file are excluded: pip does not install any of them for a consumer. ★ This repository commits no dependency lockfile that this pass reads, so each licence is the one PyPI publishes for the distribution's CURRENT release rather than for a pinned version. 5 of them publish no licence on PyPI this pass can read; that is missing data, not a violation, and none of them is charged.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Top hotspots: src/flock/core/agent.py (35×66=2310); src/flock/frontend/src/components/graph/DecisionDisplay.tsx (29×40=1160); src/flock/api/graph_builder.py (24×47=1128) Repeated repair below the complexity floor: src/flock/core/image.py (9 of 11 changes were fixes); src/flock/api/collector.py (7 of 13 changes were fixes); src/flock/core/store.py (7 of 9 changes were fixes)
Resolve the 19 Hotspot finding(s) in Churn × Complexity Hotspots — start with agent.py, DecisionDisplay.tsx, graph_builder.py. — One of this dimension's main actionable groups (19 warning-level).
Resolve the 16 Repeated repair finding(s) in Churn × Complexity Hotspots — start with image.py, collector.py, store.py. — One of this dimension's main actionable groups (16 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
11 deducted task-comment markers across 74459 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
Resolve the 11 TodoComment finding(s) in Explicit Debt — start with agents_component.py (2), TracingSettings.tsx (2), trace_component.py. — One of this dimension's main actionable groups (11 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.
The repository's root README and the beads/README are both excellent at conveying what the project is (Flock as a blackboard agent framework, Beads as an AI-native issue tracker) plus installation, usage, and contribution guidance. The READMEs of each subdirectory (e.g., examples/01-getting-started, examples/02-patterns, examples/03-hackathon, examples/04-misc) are all directory-specific READMEs that document their own purpose without claiming the repository's overview; they are well-structured and complete for their scope. The architecture/design docs (README.md + 97 markdown files) provide comprehensive coverage of the blackboard model, engines, decision models, Microsoft Foundry hosted agents, and more. The repository's READMEs are well-structured and complete for their respective directories. The examples directory (06-agent-components through 14-foundry) documents per-directory use cases with clear headings, diagrams, code blocks, and run commands; the READMEs all open with an overview of what the project is and why it matters, then dive into specific patterns, prerequisites, usage, and a full outline. The architecture/design docs (97 markdown files) are not shown in this summary but would have documented the broader system. The repository's documentation is comprehensive and well-structured: the READMEs for each directory (e.g. examples/15-decisions/, tests/e2e/, examples/app-sketches/) document their own directories rather than the root repo, with clear project descriptions, usage examples, run commands, acceptance criteria, and architecture sketches; there is also a dedicated architecture/design docs set (README.md + 97 markdown files) covering topics like Dapr demos, Foundry integration, and self-improving workflows. The internal jargon ('FlockApplication', 'Correlation ID') is consistent across the documents.
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR QualityExemplary◐ Sampled · advisory
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.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.
0 naming inconsistencies across 0 sampled symbols.
✓ On the Gold path — maintain.
Detailed fixes: d21_recommendation.md.
Do you agree with this assessment?
D22 · Internal API ConsistencyStrong◐ Sampled · advisory
What it measures: Whether the internal API surface is consistent and coherent.
Method: Judged by language model at low temperature over a sample of the public API surface (IsPackable or .Contracts types). Sampled, advisory; confidence discounted by model uncertainty.
3 API inconsistencies across a 400-member sample of 452 exposed types.
Redundant naming for synchronous/asynchronous execution. The distinction between `run` and `run_async` is implicit in the name but explicit in the signature only by convention (or lack of return type). It is more consistent to use `start`/`start_async` or `serve`/`serve_async` to clearly indicate lifecycle management rather than execution style, or to have a single `start` method that handles both via a parameter.
Ambiguous intent of 'execute'. In `RunHandle`, `execute` likely triggers the actual agent run. In `Pipeline`, `execute` likely triggers the entire chain. While technically distinct scopes, the method name is identical. If `RunHandle` is a component of a `Pipeline`, the naming is consistent. However, `RunHandle` also has `then`, suggesting a builder pattern, while `Pipeline` also has `then`. The duplication of `then` and `execute` on both types suggests they might be interchangeable or one is a wrapper for the other, creating confusion about whether to use the Handle or the Pipeline for execution.
Duplicate lifecycle hook interfaces. `ComponentLifecycle` and `AgentComponent` expose nearly identical lifecycle methods (`run_*` vs `on_*`) with the same signatures and intent (pre/post consume, evaluate, publish, error, terminate). This creates two parallel ways to hook into the agent lifecycle, confusing users about which interface to implement.
What to do
Resolve the 1 Redundant naming for synchronous/asynchronous execution. The distinction… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Ambiguous intent of 'execute'. In `RunHandle`, `execute` likely triggers… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Duplicate lifecycle hook interfaces. `ComponentLifecycle` and… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d22_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the code actually follows the decisions recorded in the project's ADRs.
Method: Judged by language model at low temperature against ADRs plus a deterministic structural code summary; findings linked to repo-rooted ADR paths for traceability. Advisory.
2 of 2 build units (Python, npm) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
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
REDACTED
What to do
Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
16 finding(s): 0 critical, 14 high, 2 medium, 0 low. 10 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `src/flock/core/artifacts.py` (line 17) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
No action in Static Analysis (SAST) — all 10 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (10 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.
Resolve the 3 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 Critical vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
8 of 203 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/flock/components/server/auth/auth_component.py. Counted over 203 of the 289 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
+ 3 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether 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.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 6 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
✓ On the Gold path — maintain.
Detailed fixes: d44_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives10.0 / 10Exemplary○ Nothing flagged
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.
Do you agree with this assessment?
AC2 · Forms & labels6.1 / 10Adequate✓ Tool-verified
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
This control has 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. (×6) — src/flock/frontend/src/components/filters/CorrelationIDFilter.tsx:73, src/flock/frontend/src/components/modules/TraceModuleJaeger.tsx:901, src/flock/frontend/src/components/settings/AppearanceSettings.tsx:61, …
This <div> carries a click handler, which makes it a control, and its only name is a title attribute. A plain element maps to role="generic", which does not support a name from the author, so the title is announced as nothing at all — it is a mouse-only tooltip, unreachable on touch. Give it role="button" (which it needs anyway to be operable) so the title becomes a real name, or add an aria-label. — src/flock/frontend/src/components/modules/TraceModuleJaeger.tsx:612
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. (×4) — src/flock/frontend/src/components/settings/ThemeSelector.tsx:142, src/flock/frontend/src/components/settings/ThemeSelector.tsx:177, src/flock/frontend/src/components/settings/ThemeSelector.tsx:203, …
What to do
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
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. (×8) — src/flock/frontend/src/components/details/MessageHistoryTab.tsx:284, src/flock/frontend/src/components/filters/CorrelationIDFilter.tsx:101, src/flock/frontend/src/components/graph/LogicOperationsDisplay.tsx:177, …
This <tr> 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. — src/flock/frontend/src/components/details/RunStatusTab.tsx:245
This <aside role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close. — src/flock/frontend/src/components/filters/FilterFlyout.tsx:17
This <div> binds double-click and nothing else. No click, no key handler, and no tabIndex={0}, so it cannot even take focus. Nothing synthesises a double-click from the keyboard: Enter and Space fire a single click, and only on a native <button> or <a href>. So this behaviour has no keyboard path at all. Expose the same action on a real control, or add role + tabIndex={0} + a key handler alongside the double-click. — src/flock/frontend/src/components/graph/AgentNode.tsx:157
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. (×7) — src/flock/frontend/src/components/graph/GraphCanvas.tsx:507, src/flock/frontend/src/components/graph/GraphCanvas.tsx:733, src/flock/frontend/src/components/graph/MessageFlowEdge.tsx:102, …
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}. — src/flock/frontend/src/components/settings/MultiSelect.tsx:213
What to do
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.
Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Do you agree with this assessment?
AC7 · A11y enforcement4.0 / 10Weak✓ Tool-verified
Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an accessibility checker configured over the markup (an a11y lint rule set, e.g. eslint-plugin-jsx-a11y or vuejs-accessibility where the project lints JavaScript) and an automated accessibility assertion wired into tests or CI (axe/pa11y/Lighthouse or an equivalent) — on the Documented→Verified→Prevented ladder.
Method: Repo config/CI scan: an accessibility checker configured over the markup (an a11y lint rule set such as eslint-plugin-jsx-a11y / vuejs-accessibility where JavaScript is linted) and an automated accessibility assertion in tests or CI (axe/pa11y/Lighthouse or equivalent), graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.
Coverage: Population: the repository's own tooling configuration — lint config, test and CI files — NOT the markup. It is read for a configured accessibility checker and an automated accessibility assertion (axe/pa11y/Lighthouse, or a native-toolkit equivalent), and it credits an INVOCATION, never a mention: a licence filename, an import comment or a doc reference earns no rung. Enforcement configured entirely outside the repository leaves no evidence here and cannot be credited.
No accessibility enforcement found — no a11y linter (eslint-plugin-jsx-a11y) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 53 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.
What to do
Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with vitest-axe in tests, then gate axe/pa11y/Lighthouse in CI.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
What to do
The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
`SettingsState` declares 20 required operations: `setShowFilters`, `setShowControls`, `setShowSettings`, `setEdgeType`, `setEdgeStrokeWidth`, `setEdgeAnimation`, `setShowEdgeLabels`, `setTheme`, `setAgentIdleColor`, `setAgentActiveColor`, `setAgentErrorColor`, `setNodeShadow`, `setShowStatusPulse`, `setCompactNodeView`, `setLayoutDirection`, `setNodeSpacing`, `setRankSpacing`, `setDebugMode`, `setPerformanceMode`, `resetToDefaults`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/flock/frontend/src/store/settingsStore.ts:11
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Do you agree with this assessment?
C2 · Access Controls4.7 / 10Weak✓ Tool-verified
Other · Security — Whether access is authorized by default — a framework authorization attribute/decorator or policy, or imperative guard methods (throw-on-violation) called from handlers.
Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.
Only 1 place(s) refuse an unauthorized caller — too few to demonstrate default-deny across handlers.
What to do
Enforce authorization at every handler — a guard on each route, or a global authentication guard/middleware with explicit public opt-outs, so protected-by-default is demonstrable.
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
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
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.
2 ADR-shaped document(s) detected by content — `examples/15-decisions/README.md`, `openspec/changes/archive/2026-02-17-openclaw-multi-output-envelope/design.md`. They are not under a conventional ADR folder (docs/adr/) and are not named NNNN-title.md, and this check found them by their decision signature rather than by where they live — so a reader who does not already know these paths has no route to them. Detected by content signature only: records kept outside the repository, or written without a Status/Decision/Consequences shape, are not visible to this check and are not counted here.
What to do
Move ADRs under docs/adr/ (or docs/adrs/) and name them NNNN-title.md so they're easy to find.
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.
CONTRIBUTING.md installs `#` (`npm install # Install frontend deps`), but no package.json declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — CONTRIBUTING.md:64
CONTRIBUTING.md installs `Install` (`npm install # Install frontend deps`), but no package.json declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — CONTRIBUTING.md:64
CONTRIBUTING.md installs `frontend` (`npm install # Install frontend deps`), but no package.json declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — CONTRIBUTING.md:64
CONTRIBUTING.md installs `deps` (`npm install # Install frontend deps`), but no package.json declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — CONTRIBUTING.md:64
CONTRIBUTING.md links to `docs/VERSIONING.md`, but `docs/VERSIONING.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — CONTRIBUTING.md:269
CONTRIBUTING.md installs `package-name` (`npm install package-name`), but no package.json declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — CONTRIBUTING.md:554
CONTRIBUTING.md links to `docs/PRE_COMMIT_HOOKS.md`, but `docs/PRE_COMMIT_HOOKS.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — CONTRIBUTING.md:699
docs/architecture.md names `src/flock/store.py`, but no file or folder `src/flock/store.py` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/architecture.md:605
docs/architecture.md names `storage/sqlite/sqlite_store.py`, but no file or folder `storage/sqlite/sqlite_store.py` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/architecture.md:643
docs/architecture.md names `storage/in_memory/memory_store.py`, but no file or folder `storage/in_memory/memory_store.py` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/architecture.md:651
docs/architecture.md names `src/flock/engines/base.py`, but no file or folder `src/flock/engines/base.py` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/architecture.md:678
docs/architecture.md names `dspy/tool_executor.py`, but no file or folder `dspy/tool_executor.py` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/architecture.md:732
docs/architecture.md names `dspy/prompt_builder.py`, but no file or folder `dspy/prompt_builder.py` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/architecture.md:733
docs/architecture.md names `docs/refactor/breaking_changes.md`, but no file or folder `docs/refactor/breaking_changes.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/architecture.md:1014
docs/about/contributing.md installs `#` (`npm install # Install frontend deps`), but no package.json declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/about/contributing.md:75
docs/about/contributing.md installs `Install` (`npm install # Install frontend deps`), but no package.json declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/about/contributing.md:75
docs/about/contributing.md installs `frontend` (`npm install # Install frontend deps`), but no package.json declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/about/contributing.md:75
docs/about/contributing.md installs `deps` (`npm install # Install frontend deps`), but no package.json declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/about/contributing.md:75
docs/about/contributing.md installs `package-name` (`npm install package-name`), but no package.json declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/about/contributing.md:445
docs/guides/components.md links to `../reference/api/components.md`, but `docs/reference/api/components.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/guides/components.md:783
docs/guides/local-models.md documents the environment variable `OLLAMA_API_BASE`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/guides/local-models.md:39
docs/guides/mcp-roots.md links to `./mcp-architecture.md`, but `docs/guides/mcp-architecture.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/guides/mcp-roots.md:415
docs/guides/mcp-roots.md links to `./agent-builder.md`, but `docs/guides/agent-builder.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/guides/mcp-roots.md:416
docs/guides/orchestrator-components.md links to `../guides/custom-engines.md`, but `docs/guides/custom-engines.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/guides/orchestrator-components.md:731
docs/guides/orchestrator-components.md links to `../reference/api/orchestrator_component.md`, but `docs/reference/api/orchestrator_component.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/guides/orchestrator-components.md:734
docs/guides/silent-mode.md documents the environment variable `FLOCK_NO_OUTPUT`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/guides/silent-mode.md:231
docs/patterns/server_component_benefits.md links to `./server_component_refactoring.md`, but `docs/patterns/server_component_refactoring.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/patterns/server_component_benefits.md:334
docs/reference/index.md documents the environment variable `FLOCK_DASHBOARD_PORT`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/reference/index.md:91
docs/reference/index.md documents the environment variable `FLOCK_DASHBOARD_HOST`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/reference/index.md:94
docs/reference/index.md documents the environment variable `TYPE_MISMATCH`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/reference/index.md:263
docs/reference/index.md documents the environment variable `VISIBILITY_DENIED`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/reference/index.md:264
docs/reference/index.md documents the environment variable `TRACE_DB_ERROR`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/reference/index.md:265
docs/reference/index.md documents the environment variable `ENGINE_ERROR`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/reference/index.md:266
docs/tutorials/conditional-routing.md links to `../reference/api/agent.md`, but `docs/reference/api/agent.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/tutorials/conditional-routing.md:332
docs/tutorials/connect_with_ollama.md documents the environment variable `OLLAMA_HOST`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/tutorials/connect_with_ollama.md:20
docs/tutorials/connect_with_ollama.md documents the environment variable `TRELLIS_MODEL`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/tutorials/connect_with_ollama.md:32
docs/tutorials/connect_with_ollama.md documents the environment variable `OLLAMA_API_BASE`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/tutorials/connect_with_ollama.md:33
docs/tutorials/connect_with_ollama.md documents the environment variable `OPENAI_MODEL`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/tutorials/connect_with_ollama.md:54
docs/tutorials/multi-agent-workflow.md links to `../reference/api/agent.md`, but `docs/reference/api/agent.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/tutorials/multi-agent-workflow.md:382
docs/tutorials/your-first-agent.md links to `../reference/api/agent.md`, but `docs/reference/api/agent.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/tutorials/your-first-agent.md:225
What to do
Reconcile the README with reality: CONTRIBUTING.md installs `#` (`npm install # Install frontend deps`), but no package.json declares it; CONTRIBUTING.md installs `Install` (`npm install # Install frontend deps`), but no package.json declares it; CONTRIBUTING.md installs `frontend` (`npm install # Install frontend deps`), but no package.json declares it; CONTRIBUTING.md installs `deps` (`npm install # Install frontend deps`), but no package.json declares it; CONTRIBUTING.md links to `docs/VERSIONING.md`, but `docs/VERSIONING.md` does not exist.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language 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.
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 bandit, `semgrep --config=p/python`, or CodeQL's python pack as a CI step. What was searched, so you can tell an absence from a miss: the 4100 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.
What to do
Add a SAST step to CI running what this repository's stack ships: bandit, `semgrep --config=p/python`, or CodeQL's python pack — so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
Do you agree with this assessment?
P5 · DR & Backup7.0 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.
Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.
What to do
Enable purge protection / soft-delete (and prevent_destroy on critical resources) so data stores can't be lost to an accidental or malicious delete.
Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.
Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.
Readiness · 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.
Do you agree with this assessment?
R1 · Type Safety10.0 / 10Exemplary✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
React / JS · Code Health — 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.
11 duplicated blocks under src/flock/frontend/src/components/ have copies in at least two of the sibling directories common, controls, details, filters, graph, layout (+2 more sibling(s) not listed) — 6 of them are reported below, and 5 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 11 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 11 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 11 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/flock/frontend/src/components/common/ImageThumbnails.tsx:25
src/flock/frontend/src/components/graph/PendingBatchEdge.tsx:1 · src/flock/frontend/src/components/graph/PendingJoinEdge.tsx:1 — these 2 files are line-for-line copies of one another — 62 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — src/flock/frontend/src/components/graph/PendingBatchEdge.tsx:1
src/flock/frontend/src/components/details/MessageDetailWindow.tsx:62 · src/flock/frontend/src/components/details/NodeDetailWindow.tsx:31 — 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. — src/flock/frontend/src/components/details/MessageDetailWindow.tsx:62
src/flock/frontend/src/components/settings/AppearanceSettings.tsx:122 · src/flock/frontend/src/components/settings/GraphSettings.tsx:27 — the two spans are one implementation copied and then locally edited — 282 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. — src/flock/frontend/src/components/settings/AppearanceSettings.tsx:122
src/flock/frontend/src/components/graph/MessageFlowEdge.tsx:31 · src/flock/frontend/src/components/graph/TransformEdge.tsx:27 — the two spans are one implementation copied and then locally edited — 278 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. — src/flock/frontend/src/components/graph/MessageFlowEdge.tsx:31
src/flock/frontend/src/components/details/MessageHistoryTab.tsx:156 · src/flock/frontend/src/components/details/RunStatusTab.tsx:113 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/flock/frontend/src/components/details/MessageHistoryTab.tsx:156
src/flock/frontend/src/components/graph/GraphCanvas.tsx:476 · src/flock/frontend/src/components/graph/GraphCanvas.tsx:700 — 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. — src/flock/frontend/src/components/graph/GraphCanvas.tsx:476
src/flock/frontend/src/store/graphStore.ts:135 · src/flock/frontend/src/store/graphStore.ts:191 — 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. — src/flock/frontend/src/store/graphStore.ts:135
src/flock/frontend/src/components/details/MessageDetailWindow.tsx:158 · src/flock/frontend/src/components/details/NodeDetailWindow.tsx:117 — 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. — src/flock/frontend/src/components/details/MessageDetailWindow.tsx:158
src/flock/frontend/src/store/moduleStore.ts:29 · src/flock/frontend/src/store/uiStore.ts:89 — the two spans are one implementation copied and then locally edited — 196 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. — src/flock/frontend/src/store/moduleStore.ts:29
src/flock/frontend/src/components/settings/AdvancedSettings.tsx:101 · src/flock/frontend/src/components/settings/GraphSettings.tsx:55 — 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. — src/flock/frontend/src/components/settings/AdvancedSettings.tsx:101
src/flock/frontend/src/components/settings/AdvancedSettings.tsx:14 · src/flock/frontend/src/components/settings/GraphSettings.tsx:14 — the two spans are one implementation copied and then locally edited — 260 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. — src/flock/frontend/src/components/settings/AdvancedSettings.tsx:14
src/flock/frontend/src/components/details/MessageHistoryTab.tsx:210 · src/flock/frontend/src/components/details/RunStatusTab.tsx:174 — the 2 copies are spread across 2 files, and what repeats is a LIST OF ENTRIES rather than behaviour — the same entries written out more than once. Extract them into one shared, exported constant and spread that constant into each site, rather than into a function the sites call: a list like this often lives in declarative metadata (a decorator's options object, a static configuration table) that a build step must be able to read statically, where a function call is not allowed. Adding an entry to one copy and not the other is the failure this prevents. — src/flock/frontend/src/components/details/MessageHistoryTab.tsx:210
src/flock/frontend/src/components/settings/ThemeSelector.tsx:204 · src/flock/frontend/src/components/settings/ThemeSelector.tsx:244 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/flock/frontend/src/components/settings/ThemeSelector.tsx:204
src/flock/frontend/src/components/controls/PublishControl.tsx:472 · src/flock/frontend/src/components/controls/PublishControl.tsx:499 — 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. — src/flock/frontend/src/components/controls/PublishControl.tsx:472
src/flock/frontend/src/services/layout.ts:390 · src/flock/frontend/src/services/layout.ts:503 — 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. — src/flock/frontend/src/services/layout.ts:390
src/flock/frontend/src/components/graph/GraphCanvas.tsx:523 · src/flock/frontend/src/components/graph/GraphCanvas.tsx:546 · src/flock/frontend/src/components/graph/GraphCanvas.tsx:569 · src/flock/frontend/src/components/graph/GraphCanvas.tsx:592 · +1 more site(s) not listed — all 5 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. — src/flock/frontend/src/components/graph/GraphCanvas.tsx:523
src/flock/frontend/src/components/settings/AppearanceSettings.tsx:47 · src/flock/frontend/src/components/settings/AppearanceSettings.tsx:72 · src/flock/frontend/src/components/settings/AppearanceSettings.tsx:97 — 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. — src/flock/frontend/src/components/settings/AppearanceSettings.tsx:47
src/flock/frontend/src/store/graphStore.ts:276 · src/flock/frontend/src/store/graphStore.ts:308 — 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. — src/flock/frontend/src/store/graphStore.ts:276
src/flock/frontend/src/components/common/ImageThumbnails.tsx:25 · src/flock/frontend/src/components/graph/TournamentBracket.tsx:110 — 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. — src/flock/frontend/src/components/common/ImageThumbnails.tsx:25
src/flock/frontend/src/services/api.ts:199 · src/flock/frontend/src/services/api.ts:261 — 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. — src/flock/frontend/src/services/api.ts:199
src/flock/frontend/src/components/modules/TraceModuleJaeger.tsx:974 · src/flock/frontend/src/components/modules/TraceModuleJaeger.tsx:1086 — 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. — src/flock/frontend/src/components/modules/TraceModuleJaeger.tsx:974
src/flock/frontend/src/App.tsx:89 · src/flock/frontend/src/components/modules/HistoricalArtifactsModule.tsx:105 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — src/flock/frontend/src/App.tsx:89
src/flock/frontend/src/components/details/MessageHistoryTab.tsx:298 · src/flock/frontend/src/components/details/RunStatusTab.tsx:272 — 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. — src/flock/frontend/src/components/details/MessageHistoryTab.tsx:298
src/flock/frontend/src/components/modules/JsonAttributeRenderer.tsx:46 · src/flock/frontend/src/components/modules/JsonAttributeRenderer.tsx:67 — 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. — src/flock/frontend/src/components/modules/JsonAttributeRenderer.tsx:46
src/flock/frontend/src/components/settings/TracingSettings.tsx:194 · src/flock/frontend/src/components/settings/TracingSettings.tsx:213 — 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. — src/flock/frontend/src/components/settings/TracingSettings.tsx:194
src/flock/frontend/src/components/details/MessageHistoryTab.tsx:49 · src/flock/frontend/src/components/details/MessageHistoryTab.tsx:96 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — src/flock/frontend/src/components/details/MessageHistoryTab.tsx:49
src/flock/frontend/src/components/layout/DashboardLayout.tsx:143 · src/flock/frontend/src/components/layout/DashboardLayout.tsx:164 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — src/flock/frontend/src/components/layout/DashboardLayout.tsx:143
src/flock/frontend/src/services/api.ts:122 · src/flock/frontend/src/services/api.ts:152 · src/flock/frontend/src/services/api.ts:335 · src/flock/frontend/src/services/api.ts:364 — 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. — src/flock/frontend/src/services/api.ts:122
src/flock/frontend/src/services/indexeddb.ts:556 · src/flock/frontend/src/services/indexeddb.ts:606 · src/flock/frontend/src/services/indexeddb.ts:656 · src/flock/frontend/src/services/indexeddb.ts:706 — 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. — src/flock/frontend/src/services/indexeddb.ts:556
src/flock/frontend/src/components/controls/PublishControl.tsx:632 · src/flock/frontend/src/components/settings/SettingsPanel.tsx:46 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — src/flock/frontend/src/components/controls/PublishControl.tsx:632
src/flock/frontend/src/components/settings/AppearanceSettings.tsx:16 · src/flock/frontend/src/components/settings/GraphSettings.tsx:14 — 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. — src/flock/frontend/src/components/settings/AppearanceSettings.tsx:16
src/flock/frontend/src/services/indexeddb.ts:439 · src/flock/frontend/src/services/indexeddb.ts:526 · src/flock/frontend/src/services/indexeddb.ts:576 · src/flock/frontend/src/services/indexeddb.ts:626 · +1 more site(s) not listed — 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. — src/flock/frontend/src/services/indexeddb.ts:439
src/flock/frontend/src/components/controls/PublishControl.tsx:526 · src/flock/frontend/src/components/controls/PublishControl.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. — src/flock/frontend/src/components/controls/PublishControl.tsx:526
src/flock/frontend/src/components/graph/AgentNode.tsx:247 · src/flock/frontend/src/components/graph/AgentNode.tsx:310 — 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. — src/flock/frontend/src/components/graph/AgentNode.tsx:247
src/flock/frontend/src/components/graph/DecisionDisplay.tsx:379 · src/flock/frontend/src/components/graph/DecisionDisplay.tsx:773 — 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. — src/flock/frontend/src/components/graph/DecisionDisplay.tsx:379
src/flock/frontend/src/components/settings/TracingSettings.tsx:258 · src/flock/frontend/src/components/settings/TracingSettings.tsx:274 — 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. — src/flock/frontend/src/components/settings/TracingSettings.tsx:258
src/flock/frontend/src/services/api.ts:331 · src/flock/frontend/src/services/api.ts:360 — 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. — src/flock/frontend/src/services/api.ts:331
src/flock/frontend/src/services/layout.ts:167 · src/flock/frontend/src/services/layout.ts:264 — 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. — src/flock/frontend/src/services/layout.ts:167
src/flock/frontend/src/components/controls/PublishControl.tsx:549 · src/flock/frontend/src/components/controls/PublishControl.tsx:580 — 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. — src/flock/frontend/src/components/controls/PublishControl.tsx:549
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
renderField has cyclomatic complexity 56 and cognitive complexity 64; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/flock/frontend/src/components/controls/PublishControl.tsx:320
(anonymous) has cyclomatic complexity 43 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — src/flock/frontend/src/components/graph/DecisionDisplay.tsx:1254
(anonymous) has cyclomatic complexity 37 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/flock/frontend/src/components/graph/AgentNode.tsx:12
handleKeyDown has cyclomatic complexity 33 and cognitive complexity 46; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/flock/frontend/src/hooks/useKeyboardShortcuts.ts:28
updateFilterStateFromPublishedMessage has cyclomatic complexity 33 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/flock/frontend/src/services/websocket.ts:63
TraceModuleJaeger has cyclomatic complexity 29 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — src/flock/frontend/src/components/modules/TraceModuleJaeger.tsx:73
(anonymous) has cyclomatic complexity 27 and cognitive complexity 34; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/flock/frontend/src/components/controls/PublishControl.tsx:131
resolveNodeOverlaps has cyclomatic complexity 26 and cognitive complexity 60; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/flock/frontend/src/services/layout.ts:147
(anonymous) has cyclomatic complexity 22 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/flock/frontend/src/components/controls/PublishControl.tsx:228
HistoricalArtifactsModule has cyclomatic complexity 22 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/flock/frontend/src/components/modules/HistoricalArtifactsModule.tsx:41
(anonymous) has cyclomatic complexity 21 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/flock/frontend/src/components/graph/ScheduledAgentDisplay.tsx:78
(anonymous) has cyclomatic complexity 21 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/flock/frontend/src/components/graph/LogicOperationsDisplay.tsx:131
handleMessage has cyclomatic complexity 19 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/flock/frontend/src/services/websocket.ts:511
(anonymous) 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. — src/flock/frontend/src/components/graph/ScheduledAgentDisplay.tsx:26
DashboardLayout has cyclomatic complexity 17 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/flock/frontend/src/components/layout/DashboardLayout.tsx:21
(anonymous) has cyclomatic complexity 17 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. — src/flock/frontend/src/components/modules/TraceModuleJaeger.tsx:505
MessageDetailWindow has cyclomatic complexity 16 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/flock/frontend/src/components/details/MessageDetailWindow.tsx:12
(anonymous) has cyclomatic complexity 16 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. — src/flock/frontend/src/components/graph/LogicOperationsDisplay.tsx:323
ThemeSelector has cyclomatic complexity 15 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. — src/flock/frontend/src/components/settings/ThemeSelector.tsx:14
(anonymous) has cyclomatic complexity 15 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/flock/frontend/src/components/graph/MessageNode.tsx:8
What to do
Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
Do you agree with this assessment?
R3 · Large Files4.0 / 10Weak✓ 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.
src/flock/frontend/src/components/modules/TraceModuleJaeger.tsx has 1441 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/flock/frontend/src/components/modules/TraceModuleJaeger.tsx:1
src/flock/frontend/src/components/graph/DecisionDisplay.tsx has 1317 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/flock/frontend/src/components/graph/DecisionDisplay.tsx:1
src/flock/frontend/src/services/indexeddb.ts has 738 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/flock/frontend/src/services/indexeddb.ts:1
src/flock/frontend/src/components/graph/GraphCanvas.tsx has 732 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/flock/frontend/src/components/graph/GraphCanvas.tsx:1
src/flock/frontend/src/components/controls/PublishControl.tsx has 684 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/flock/frontend/src/components/controls/PublishControl.tsx:1
src/flock/frontend/src/services/websocket.ts has 655 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/flock/frontend/src/services/websocket.ts:1
src/flock/frontend/src/services/layout.ts has 519 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/flock/frontend/src/services/layout.ts:1
src/flock/frontend/src/components/graph/LogicOperationsDisplay.tsx has 431 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/flock/frontend/src/components/graph/LogicOperationsDisplay.tsx:1
src/flock/frontend/src/store/graphStore.ts has 426 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/flock/frontend/src/store/graphStore.ts:1
src/flock/frontend/src/components/details/MessageDetailWindow.tsx has 421 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/flock/frontend/src/components/details/MessageDetailWindow.tsx:1
src/flock/frontend/src/components/graph/AgentNode.tsx has 415 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/flock/frontend/src/components/graph/AgentNode.tsx:1
src/flock/frontend/src/components/modules/HistoricalArtifactsModule.tsx has 411 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/flock/frontend/src/components/modules/HistoricalArtifactsModule.tsx:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Do you agree with this assessment?
R4 · Test Coverage9.3 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.
Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.
No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×5) — src/flock/frontend/src/components/common/EmptyState.tsx:1, src/flock/frontend/src/utils/mockData.ts:1, src/flock/frontend/src/components/common/LoadingSpinner.tsx:1, …
What to do
Add tests that import the unreached modules (directly or through their public entry).
React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).
Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.
What to do
Bump outdated dependencies to current versions to limit upgrade debt.
Do you agree with this assessment?
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.
Do you agree with this assessment?
R7 · Dead Code9.4 / 10Exemplary✓ 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, 4 tooling and 34 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, 4 tooling, 34 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 (×4) — src/flock/frontend/src/components/common/EmptyState.tsx, src/flock/frontend/src/utils/mockData.ts, src/flock/frontend/src/components/common/LoadingSpinner.tsx, …
Nothing imports this binding — it is safe to review for removal. (×5) — src/flock/frontend/src/services/layout.ts:598, src/flock/frontend/src/services/themeApplicator.ts:129, src/flock/frontend/src/types/graph.ts:98, …
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Declared in src/flock/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.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
Other · 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.
The function passed to `new Promise(…)` is `async`. The constructor ignores what its executor returns, so anything this executor throws — every throw inside an `async` function, including after an `await` — rejects a Promise nobody holds instead of the one being constructed: the outer Promise never settles, whoever awaits it hangs, and the error is reported nowhere. If the body needs `await`, it does not need `new Promise` at all: make the enclosing function `async` and `return` the value (or `throw`) directly. If it wraps a callback API, keep the executor synchronous — call the API and `resolve`/`reject` from its callback — and do the awaiting outside it. — src/flock/frontend/src/services/indexeddb.ts:170
The task this creates is not kept anywhere. The event loop holds only a weak reference to its tasks, so a task nobody references can be garbage-collected before it finishes (Python's documentation for `asyncio.create_task`: save a reference to the result); and nothing ever awaits it, so an exception it raises is never handled — it surfaces, if at all, as "Task exception was never retrieved" in a log. Keep the task: `await` it, gather it, start it in an `asyncio.TaskGroup` (`async with asyncio.TaskGroup() as tg: tg.create_task(…)`), or, for genuine fire-and-forget, add it to a set and `task.add_done_callback(tasks.discard)` with a callback that also reads its exception. — src/flock/patches/dspy_streaming_patch.py:41
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.
Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document2.4 / 10Weak✓ Tool-verified
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.
`find_images` is public, takes a document from its caller (line 73) and hands it to `_locate_images`, which calls itself at line 55 (`_locate_images`) with a piece of `value` (and at line 58) — and nowhere in `_locate_images` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. Python's parsers accept far more nesting than its stack allows: `json.loads` turns 3,000 bytes of brackets into 1,500 levels and `xml.etree.ElementTree` parses tens of thousands, while a walk like this one raises `RecursionError` once it passes the interpreter's default limit of 1,000 frames. Wherever that exception lands, the work fails: a request errors, and outside any `try` the worker or the program exits with it. Raising `sys.setrecursionlimit` only moves the number the document has to beat. Thread a depth argument through `_locate_images` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — src/flock/api/thumbnails.py:55
`compact` is public and takes `value: Any` from its caller, and it calls itself at line 89 (`compact`) with a piece of `value` (and at line 91) — and nowhere in `compact` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. Python's parsers accept far more nesting than its stack allows: `json.loads` turns 3,000 bytes of brackets into 1,500 levels and `xml.etree.ElementTree` parses tens of thousands, while a walk like this one raises `RecursionError` once it passes the interpreter's default limit of 1,000 frames. Wherever that exception lands, the work fails: a request errors, and outside any `try` the worker or the program exits with it. Raising `sys.setrecursionlimit` only moves the number the document has to beat. Thread a depth argument through `compact` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — src/flock/api/thumbnails.py:89
`check_inline_images` is public and takes `value: Any` from its caller, and it calls itself at line 216 (`check_inline_images`) with a piece of `value` (and at line 219) — and nowhere in `check_inline_images` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. Python's parsers accept far more nesting than its stack allows: `json.loads` turns 3,000 bytes of brackets into 1,500 levels and `xml.etree.ElementTree` parses tens of thousands, while a walk like this one raises `RecursionError` once it passes the interpreter's default limit of 1,000 frames. Wherever that exception lands, the work fails: a request errors, and outside any `try` the worker or the program exits with it. Raising `sys.setrecursionlimit` only moves the number the document has to beat. Thread a depth argument through `check_inline_images` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — src/flock/core/image.py:216
`imageFieldKind` is exported and takes `prop: any` from its caller, and it calls itself at line 33 (`imageFieldKind`) with a piece of `prop` — and nowhere in `imageFieldKind` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `imageFieldKind` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — src/flock/frontend/src/utils/imageFields.ts:33
`deserialize_visibility` is public, takes a document from its caller (line 71) and hands it to `_validate_visibility`, which calls itself at line 170 (`_validate_visibility`) with a piece of `data` — and nowhere in `_validate_visibility` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. Python's parsers accept far more nesting than its stack allows: `json.loads` turns 3,000 bytes of brackets into 1,500 levels and `xml.etree.ElementTree` parses tens of thousands, while a walk like this one raises `RecursionError` once it passes the interpreter's default limit of 1,000 frames. Wherever that exception lands, the work fails: a request errors, and outside any `try` the worker or the program exits with it. Raising `sys.setrecursionlimit` only moves the number the document has to beat. Thread a depth argument through `_validate_visibility` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — src/flock/utils/visibility_utils.py:170
What to do
Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether async functions that make a cancellable request accept or pass on an AbortSignal (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.
Only 0/17 async functions that make a cancellable request (fetch, axios, ky, ofetch) 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.
`fetchRunHistory` 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 })`. — src/flock/frontend/src/components/details/RunStatusTab.tsx:29
`fetchMessageHistory` 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 })`. — src/flock/frontend/src/components/details/MessageHistoryTab.tsx:36
`fetchHistory` 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 })`. — src/flock/frontend/src/components/details/LiveOutputTab.tsx:24
`fetchTraces` 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 })`. — src/flock/frontend/src/components/modules/TraceModuleJaeger.tsx:142
`loadTraceServices` 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 })`. — src/flock/frontend/src/components/settings/TracingSettings.tsx:56
`loadTraceStats` 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 })`. — src/flock/frontend/src/components/settings/TracingSettings.tsx:68
`fetchVersion` 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 })`. — src/flock/frontend/src/components/settings/AdvancedSettings.tsx:33
`fetchThemeList` 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 })`. — src/flock/frontend/src/services/themeService.ts:15
`fetchTheme` 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 })`. — src/flock/frontend/src/services/themeService.ts:39
`fetchArtifactTypes` 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 })`. — src/flock/frontend/src/services/api.ts:120
`fetchAgents` 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 })`. — src/flock/frontend/src/services/api.ts:150
`publishArtifact` 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 })`. — src/flock/frontend/src/services/api.ts:187
`reviewDecision` 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 })`. — src/flock/frontend/src/services/api.ts:232
`invokeAgent` 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 })`. — src/flock/frontend/src/services/api.ts:253
`fetchArtifact` 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 })`. — src/flock/frontend/src/services/api.ts:316
`fetchArtifacts` 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 })`. — src/flock/frontend/src/services/api.ts:331
`fetchArtifactSummary` 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 })`. — src/flock/frontend/src/services/api.ts:360
What to do
Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether 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.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
`debug` at line 682 is called with an argument built by `[r.uri for r in self.current_roots]` (line 684), whose cost grows with the collection it walks. Python evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isEnabledFor(logging.DEBUG)` test, no debug flag, no `lambda` the logger calls only when the level is on. — src/flock/mcp/client.py:682
What to do
In Python, put the construction behind the logger's own check (`if logger.isEnabledFor(logging.DEBUG):`), or pass the collection itself with a `%s` placeholder (`logger.debug("Items %s", items)`) so the logging module renders it only when the record is emitted. The placeholder alone is not the fix when the argument is still built first: it defers the formatting, not a `json.dumps`, a `join` or a comprehension in the argument, and an f-string defers nothing at all.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged
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.
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.
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.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — 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.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
`except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×20) — scripts/generate_llm_codebase.py:113, src/flock/components/server/control/control_routes_component.py:111, src/flock/components/server/control/control_routes_component.py:123, …
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×4) — scripts/generate_llm_codebase.py:224, src/flock/frontend/src/services/indexeddb.ts:264, src/flock/integrations/openclaw/streaming.py:484, …
`.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. — src/flock/frontend/src/components/graph/LogicOperationsDisplay.tsx:85
What to do
Swallowed exception (caught, then discarded)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
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.8 `!` null assertions per 1k TypeScript source lines — 14 assertion(s) across the 18133 source line(s) of the 80 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: src/flock/frontend/src/components/modules/TraceModuleJaeger.tsx (7), src/flock/frontend/src/components/graph/LogicOperationsDisplay.tsx (2), src/flock/frontend/src/services/layout.ts (2). 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 `?`).
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 2 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
X10 Duplicated predicate — 19 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 6 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Not assessed: this repository stores data through 'duckdb' (src/flock/components/server/traces/trace_component.py:10) but declares no persisted model this check reads (Django, SQLAlchemy, SQLModel, Peewee, Tortoise and MongoEngine model fields, Alembic and Django migration columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL files). Personal data may be written through raw SQL or a hosted backend, so whether its changes need an audit trail could not be established, and the trail's absence is not scored.
C4 Data Retention — Not assessed: this repository stores data through 'duckdb' (src/flock/components/server/traces/trace_component.py:10) but declares no persisted model this check reads (Django, SQLAlchemy, SQLModel, Peewee, Tortoise and mongoengine model fields, Alembic and Django migration columns, SQL schemas). Personal data may be written through raw SQL or a hosted backend, so whether a retention limit applies here could not be established, and its absence is not scored.
C5 Data-Subject Rights — Not assessed: this repository stores data through 'duckdb' (src/flock/components/server/traces/trace_component.py:10) but declares no persisted model this check reads (Django, SQLAlchemy, SQLModel, Peewee, Tortoise and mongoengine model fields, Alembic and Django migration columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL files). Personal data may be written through raw SQL or a hosted backend, so whether data-subject rights apply here could not be established, and their absence is not scored.
Not included — 39 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX2 Stateful singletons — 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. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — compose up failed (exit 18 — an image could not be pulled) — scheduler Pulling flock-dapr Pulling placement Pulling flock-dapr Error Get "https://registry-1.docker.io/v2/": Forbidden scheduler Error Get "https://registry-1.docker.io/v2/": Forbidden placement Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: placement Pulling flock-dapr Pulling scheduler Pulling placement Error Get "https://registry-1.docker.io/v2/": Forbidden flock-dapr Error Get "https://registry-1.docker.io/v2/": Forbidden scheduler Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — 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.
D16 Bus Factor — single-maintainer repository — bus factor is not applicable
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
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+ projects each declaring an entity of their own. 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 — No inline comments to assess — comment value is not applicable here.
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.py), 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.
D32 Data Compliance (PII/GDPR) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
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.
D8 Code Coverage — Coverage not measured — polyglot repository, one half has no runner
DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 366 value object(s); 7 domain event(s); its domain events are published by services or handlers — no domain entity raises one
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P12 CI test-gate honesty — Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
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 — coverage data present for 64 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for a pytest-benchmark or pytest-codspeed dependency with tests taking the `benchmark` fixture, an asv.conf.json with its `time_`/`mem_`/`peakmem_` benchmarks, or a pyperf Runner, 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: Python 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.
S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
AC4 · Keyboard semantics· Hover-only interaction on <div> · ×7
Hover-only interaction on <div> src/flock/frontend/src/components/graph/GraphCanvas.tsx:507— 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.
Hover-only interaction on <div> src/flock/frontend/src/components/graph/GraphCanvas.tsx:733— 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.
Hover-only interaction on <div> src/flock/frontend/src/components/graph/MessageFlowEdge.tsx:102— 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.
Hover-only interaction on <div> src/flock/frontend/src/components/graph/PendingBatchEdge.tsx:104— 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.
Hover-only interaction on <div> src/flock/frontend/src/components/graph/PendingJoinEdge.tsx:103— 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.
Hover-only interaction on <div> src/flock/frontend/src/components/graph/TournamentBracket.tsx:290— 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.
Hover-only interaction on <div> src/flock/frontend/src/components/graph/TransformEdge.tsx:95— 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.
AC2 · Forms & labels· <input> without a programmatic label · ×6
<input> without a programmatic label src/flock/frontend/src/components/filters/CorrelationIDFilter.tsx:73— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<input> without a programmatic label src/flock/frontend/src/components/modules/TraceModuleJaeger.tsx:901— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<input> without a programmatic label src/flock/frontend/src/components/settings/AppearanceSettings.tsx:61— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<input> without a programmatic label src/flock/frontend/src/components/settings/AppearanceSettings.tsx:86— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<input> without a programmatic label src/flock/frontend/src/components/settings/AppearanceSettings.tsx:111— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<input> without a programmatic label src/flock/frontend/src/components/settings/MultiSelect.tsx:169— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
AC4 · Keyboard semantics· Click handler on a non-interactive <div> · ×6
Click handler on a non-interactive <div> src/flock/frontend/src/components/filters/CorrelationIDFilter.tsx:101— 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> src/flock/frontend/src/components/graph/LogicOperationsDisplay.tsx:177— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> src/flock/frontend/src/components/modules/TraceModuleJaeger.tsx:612— 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> src/flock/frontend/src/components/modules/TraceModuleJaeger.tsx:1119— 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> src/flock/frontend/src/components/modules/TraceModuleJaeger.tsx:1438— 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> src/flock/frontend/src/components/settings/MultiSelect.tsx:213— 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}.
AC2 · Forms & labels· <label> that labels no control · ×4
<label> that labels no control src/flock/frontend/src/components/settings/ThemeSelector.tsx:142— This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control src/flock/frontend/src/components/settings/ThemeSelector.tsx:177— 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 src/flock/frontend/src/components/settings/ThemeSelector.tsx:203— 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 src/flock/frontend/src/components/settings/ThemeSelector.tsx:232— This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
AC4 · Keyboard semantics· Click handler on a non-interactive <span> · ×2
Click handler on a non-interactive <span> src/flock/frontend/src/components/modules/TraceModuleJaeger.tsx:544— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <span> src/flock/frontend/src/components/modules/TraceModuleJaeger.tsx:570— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
AC2 · Forms & labels· Custom control named only by title on <div> · ×1
Custom control named only by title on <div> src/flock/frontend/src/components/modules/TraceModuleJaeger.tsx:612— This <div> carries a click handler, which makes it a control, and its only name is a title attribute. A plain element maps to role="generic", which does not support a name from the author, so the title is announced as nothing at all — it is a mouse-only tooltip, unreachable on touch. Give it role="button" (which it needs anyway to be operable) so the title becomes a real name, or add an aria-label.
AC4 · Keyboard semantics· Click handler on a non-interactive <tr> · ×1
Click handler on a non-interactive <tr> src/flock/frontend/src/components/details/MessageHistoryTab.tsx:284— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
AC4 · Keyboard semantics· Hover-only interaction on <tr> · ×1
Hover-only interaction on <tr> src/flock/frontend/src/components/details/RunStatusTab.tsx:245— This <tr> 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· Double-click handler on a non-interactive <div> · ×1
Double-click handler on a non-interactive <div> src/flock/frontend/src/components/graph/AgentNode.tsx:157— This <div> binds double-click and nothing else. No click, no key handler, and no tabIndex={0}, so it cannot even take focus. Nothing synthesises a double-click from the keyboard: Enter and Space fire a single click, and only on a native <button> or <a href>. So this behaviour has no keyboard path at all. Expose the same action on a real control, or add role + tabIndex={0} + a key handler alongside the double-click.
FunctionTooLong: TraceModuleJaeger.TraceModuleJaeger src/flock/frontend/src/components/modules/TraceModuleJaeger.tsx:73— FunctionTooLong — TraceModuleJaeger runs 1223 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1123 over it, 12.23× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: GraphCanvas.GraphCanvas src/flock/frontend/src/components/graph/GraphCanvas.tsx:44— FunctionTooLong — GraphCanvas runs 553 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 453 over it, 5.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: PublishControl.PublishControl src/flock/frontend/src/components/controls/PublishControl.tsx:23— FunctionTooLong — PublishControl runs 534 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 434 over it, 5.34× 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: MessageDetailWindow.MessageDetailWindow src/flock/frontend/src/components/details/MessageDetailWindow.tsx:12— FunctionTooLong — MessageDetailWindow runs 365 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 265 over it, 3.65× 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: LogicOperationsDisplay.LogicOperationsDisplay src/flock/frontend/src/components/graph/LogicOperationsDisplay.tsx:25— FunctionTooLong — LogicOperationsDisplay runs 349 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 249 over it, 3.49× 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: AgentNode.AgentNode src/flock/frontend/src/components/graph/AgentNode.tsx:12— FunctionTooLong — AgentNode runs 347 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 247 over it, 3.47× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: HistoricalArtifactsModule.HistoricalArtifactsModule src/flock/frontend/src/components/modules/HistoricalArtifactsModule.tsx:41— FunctionTooLong — HistoricalArtifactsModule runs 328 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 228 over it, 3.28× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: TracingSettings.TracingSettings src/flock/frontend/src/components/settings/TracingSettings.tsx:30— FunctionTooLong — TracingSettings runs 309 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 209 over it, 3.09× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: MessageHistoryTab.MessageHistoryTab src/flock/frontend/src/components/details/MessageHistoryTab.tsx:23— FunctionTooLong — MessageHistoryTab runs 282 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 182 over it, 2.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: RunStatusTab.RunStatusTab src/flock/frontend/src/components/details/RunStatusTab.tsx:22— FunctionTooLong — RunStatusTab runs 269 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 169 over it, 2.69× 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: TournamentBracket.TournamentBracket src/flock/frontend/src/components/graph/TournamentBracket.tsx:95— FunctionTooLong — TournamentBracket runs 229 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 129 over it, 2.29× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: DashboardLayout.DashboardLayout src/flock/frontend/src/components/layout/DashboardLayout.tsx:21— FunctionTooLong — DashboardLayout runs 206 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 106 over it, 2.06× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: ScheduledAgentDisplay.ScheduledAgentDisplay src/flock/frontend/src/components/graph/ScheduledAgentDisplay.tsx:26— FunctionTooLong — ScheduledAgentDisplay runs 186 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 86 over it, 1.86× 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: MultiSelect.MultiSelect src/flock/frontend/src/components/settings/MultiSelect.tsx:21— FunctionTooLong — MultiSelect runs 176 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 76 over it, 1.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: NodeDetailWindow.NodeDetailWindow src/flock/frontend/src/components/details/NodeDetailWindow.tsx:13— FunctionTooLong — NodeDetailWindow runs 170 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 70 over it, 1.70× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: ModuleWindow.ModuleWindow src/flock/frontend/src/components/modules/ModuleWindow.tsx:11— FunctionTooLong — ModuleWindow runs 170 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 70 over it, 1.70× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: LiveOutputTab.LiveOutputTab src/flock/frontend/src/components/details/LiveOutputTab.tsx:13— FunctionTooLong — LiveOutputTab runs 159 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 59 over it, 1.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: AppearanceSettings.AppearanceSettings src/flock/frontend/src/components/settings/AppearanceSettings.tsx:16— FunctionTooLong — AppearanceSettings runs 154 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 54 over it, 1.54× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: AdvancedSettings.AdvancedSettings src/flock/frontend/src/components/settings/AdvancedSettings.tsx:14— FunctionTooLong — AdvancedSettings runs 139 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 39 over it, 1.39× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: SavedFiltersControl.SavedFiltersControl src/flock/frontend/src/components/filters/SavedFiltersControl.tsx:6— FunctionTooLong — SavedFiltersControl runs 121 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 21 over it, 1.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: MessageNode.MessageNode src/flock/frontend/src/components/graph/MessageNode.tsx:8— FunctionTooLong — MessageNode runs 117 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 17 over it, 1.17× 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: JsonAttributeRenderer.JsonAttributeRenderer src/flock/frontend/src/components/modules/JsonAttributeRenderer.tsx:13— FunctionTooLong — JsonAttributeRenderer runs 106 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 6 over it, 1.06× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: FilterPills.FilterPills src/flock/frontend/src/components/filters/FilterPills.tsx:14— FunctionTooLong — FilterPills runs 101 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1 over it, 1.01× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Swallowed exception (caught, then discarded) scripts/generate_llm_codebase.py:113— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/flock/components/server/control/control_routes_component.py:111— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/flock/components/server/control/control_routes_component.py:123— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/flock/core/subscription.py:314— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) REDACTED:88— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) REDACTED:737— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/flock/engines/dspy/streaming_executor.py:86— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/flock/engines/dspy/streaming_executor.py:654— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/flock/engines/dspy/streaming_executor.py:803— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/flock/engines/dspy/signature_builder.py:512— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/flock/integrations/openclaw/streaming.py:221— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/flock/logging/trace_and_logged.py:176— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/flock/logging/telemetry_exporter/file_exporter.py:83— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/flock/logging/telemetry_exporter/base_exporter.py:22— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/flock/mcp/types/types.py:228— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/flock/mcp/types/types.py:315— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/flock/semantic/context_provider.py:101— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/flock/semantic/context_provider.py:107— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/flock/utils/runtime.py:355— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/flock/utils/runtime.py:386— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Hotspot: src/flock/core/agent.py src/flock/core/agent.py:803— src/flock/core/agent.py changed 35 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 66 in AgentBuilder.decides at line 803. 19 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-17..2026-10-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-17 15:22:17 +02:00' --until='2026-10-15 15:22:17 +02:00' --full-history --no-merges -- src/flock/core/agent.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/flock/frontend/src/components/graph/DecisionDisplay.tsx src/flock/frontend/src/components/graph/DecisionDisplay.tsx:1254— src/flock/frontend/src/components/graph/DecisionDisplay.tsx changed 29 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 40 in DecisionDisplay.DecisionBars at line 1254. 14 of those changes were fix/bug commits, and the other 15 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-17..2026-10-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-17 15:22:17 +02:00' --until='2026-10-15 15:22:17 +02:00' --full-history --no-merges -- src/flock/frontend/src/components/graph/DecisionDisplay.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/flock/api/graph_builder.py src/flock/api/graph_builder.py:322— src/flock/api/graph_builder.py changed 24 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 47 in GraphAssembler._build_agent_nodes at line 322. 12 of those changes were fix/bug commits, and the other 12 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-17..2026-10-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-17 15:22:17 +02:00' --until='2026-10-15 15:22:17 +02:00' --full-history --no-merges -- src/flock/api/graph_builder.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/flock/decisions/engine.py src/flock/decisions/engine.py:892— src/flock/decisions/engine.py changed 31 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in DecisionEngine._checklist_decision at line 892. 18 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-17..2026-10-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-17 15:22:17 +02:00' --until='2026-10-15 15:22:17 +02:00' --full-history --no-merges -- src/flock/decisions/engine.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/flock/frontend/src/components/controls/PublishControl.tsx src/flock/frontend/src/components/controls/PublishControl.tsx:23— src/flock/frontend/src/components/controls/PublishControl.tsx changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 146 in PublishControl.PublishControl at line 23. 5 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-17..2026-10-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-17 15:22:17 +02:00' --until='2026-10-15 15:22:17 +02:00' --full-history --no-merges -- src/flock/frontend/src/components/controls/PublishControl.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: REDACTED REDACTED:386— REDACTED changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in DSPyEngine._evaluate_internal at line 386. 9 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-17..2026-10-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-17 15:22:17 +02:00' --until='2026-10-15 15:22:17 +02:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/flock/decisions/graph.py src/flock/decisions/graph.py:174— src/flock/decisions/graph.py changed 18 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in graph.decision_view at line 174. 3 of those changes were fix/bug commits, and the other 15 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-17..2026-10-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-17 15:22:17 +02:00' --until='2026-10-15 15:22:17 +02:00' --full-history --no-merges -- src/flock/decisions/graph.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/flock/components/server/artifacts/artifacts_component.py src/flock/components/server/artifacts/artifacts_component.py:307— src/flock/components/server/artifacts/artifacts_component.py changed 16 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in ArtifactsComponent._publish_upload at line 307. 11 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-17..2026-10-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-17 15:22:17 +02:00' --until='2026-10-15 15:22:17 +02:00' --full-history --no-merges -- src/flock/components/server/artifacts/artifacts_component.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/flock/frontend/src/components/graph/AgentNode.tsx src/flock/frontend/src/components/graph/AgentNode.tsx:12— src/flock/frontend/src/components/graph/AgentNode.tsx changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 65 in AgentNode.AgentNode at line 12. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-17..2026-10-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-17 15:22:17 +02:00' --until='2026-10-15 15:22:17 +02:00' --full-history --no-merges -- src/flock/frontend/src/components/graph/AgentNode.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/flock/engines/dspy/signature_builder.py src/flock/engines/dspy/signature_builder.py:175— src/flock/engines/dspy/signature_builder.py changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in DSPySignatureBuilder.prepare_signature_for_output_group at line 175. 4 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-17..2026-10-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-17 15:22:17 +02:00' --until='2026-10-15 15:22:17 +02:00' --full-history --no-merges -- src/flock/engines/dspy/signature_builder.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/flock/decisions/calibration.py src/flock/decisions/calibration.py:96— src/flock/decisions/calibration.py changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in calibration.calibrate at line 96. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-17..2026-10-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-17 15:22:17 +02:00' --until='2026-10-15 15:22:17 +02:00' --full-history --no-merges -- src/flock/decisions/calibration.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/flock/decisions/choice.py src/flock/decisions/choice.py:144— src/flock/decisions/choice.py changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in _QuestionMeta.__new__ at line 144. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-17..2026-10-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-17 15:22:17 +02:00' --until='2026-10-15 15:22:17 +02:00' --full-history --no-merges -- src/flock/decisions/choice.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/flock/logging/telemetry.py src/flock/logging/telemetry.py:110— src/flock/logging/telemetry.py changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in TelemetryConfig.setup_tracing at line 110. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-17..2026-10-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-17 15:22:17 +02:00' --until='2026-10-15 15:22:17 +02:00' --full-history --no-merges -- src/flock/logging/telemetry.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/flock/frontend/src/components/graph/MessageNode.tsx src/flock/frontend/src/components/graph/MessageNode.tsx:8— src/flock/frontend/src/components/graph/MessageNode.tsx changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in MessageNode.MessageNode at line 8. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-17..2026-10-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-17 15:22:17 +02:00' --until='2026-10-15 15:22:17 +02:00' --full-history --no-merges -- src/flock/frontend/src/components/graph/MessageNode.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/flock/logging/trace_and_logged.py src/flock/logging/trace_and_logged.py:100— src/flock/logging/trace_and_logged.py changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in trace_and_logged._serialize_value at line 100. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-17..2026-10-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-17 15:22:17 +02:00' --until='2026-10-15 15:22:17 +02:00' --full-history --no-merges -- src/flock/logging/trace_and_logged.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/flock/frontend/src/services/websocket.ts src/flock/frontend/src/services/websocket.ts:166— src/flock/frontend/src/services/websocket.ts changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in WebSocketClient.setupEventHandlers at line 166. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-17..2026-10-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-17 15:22:17 +02:00' --until='2026-10-15 15:22:17 +02:00' --full-history --no-merges -- src/flock/frontend/src/services/websocket.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/flock/agent/output_processor.py src/flock/agent/output_processor.py:46— src/flock/agent/output_processor.py changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in OutputProcessor.make_outputs_for_group at line 46. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-17..2026-10-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-17 15:22:17 +02:00' --until='2026-10-15 15:22:17 +02:00' --full-history --no-merges -- src/flock/agent/output_processor.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/flock/frontend/src/components/details/RunStatusTab.tsx src/flock/frontend/src/components/details/RunStatusTab.tsx:22— src/flock/frontend/src/components/details/RunStatusTab.tsx changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in RunStatusTab.RunStatusTab at line 22. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-17..2026-10-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-17 15:22:17 +02:00' --until='2026-10-15 15:22:17 +02:00' --full-history --no-merges -- src/flock/frontend/src/components/details/RunStatusTab.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/flock/frontend/src/App.tsx src/flock/frontend/src/App.tsx:16— src/flock/frontend/src/App.tsx changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in App.App at line 16. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-17..2026-10-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-17 15:22:17 +02:00' --until='2026-10-15 15:22:17 +02:00' --full-history --no-merges -- src/flock/frontend/src/App.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
FileTooLong: modules/TraceModuleJaeger.tsx src/flock/frontend/src/components/modules/TraceModuleJaeger.tsx— FileTooLong — 1277 significant lines (blank, comment-only and punctuation-only lines excluded), about 96% of them inside a single declaration: TraceModuleJaeger (73-1558). The bar is 500 significant lines; this is 777 over it, 2.55× 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: graph/DecisionDisplay.tsx src/flock/frontend/src/components/graph/DecisionDisplay.tsx— FileTooLong — 1118 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 618 over it, 2.24× 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: api/graph_builder.py src/flock/api/graph_builder.py— FileTooLong — 1030 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 530 over it, 2.06× 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: openclaw/engine.py src/flock/integrations/openclaw/engine.py— FileTooLong — 993 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 493 over it, 1.99× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: core/agent.py src/flock/core/agent.py— FileTooLong — 926 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 426 over it, 1.85× 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: dapr/dapr_state_blackboard_store.py src/flock/storage/dapr/dapr_state_blackboard_store.py— FileTooLong — 849 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 349 over it, 1.70× 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: decisions/engine.py src/flock/decisions/engine.py— FileTooLong — 784 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 284 over it, 1.57× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: core/orchestrator.py src/flock/core/orchestrator.py— FileTooLong — 757 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 257 over it, 1.51× 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: application/application.py src/flock/application/application.py— FileTooLong — 689 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 189 over it, 1.38× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: core/store.py src/flock/core/store.py— FileTooLong — 609 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 109 over it, 1.22× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: graph/GraphCanvas.tsx src/flock/frontend/src/components/graph/GraphCanvas.tsx— FileTooLong — 596 significant lines (blank, comment-only and punctuation-only lines excluded), about 93% of them inside a single declaration: GraphCanvas (44-785). The bar is 500 significant lines; this is 96 over it, 1.19× 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: dspy/streaming_executor.py src/flock/engines/dspy/streaming_executor.py— FileTooLong — 591 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 91 over it, 1.18× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: artifacts/artifacts_component.py src/flock/components/server/artifacts/artifacts_component.py— FileTooLong — 587 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 87 over it, 1.17× 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: controls/PublishControl.tsx src/flock/frontend/src/components/controls/PublishControl.tsx— FileTooLong — 549 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: PublishControl (23-736). The bar is 500 significant lines; this is 49 over it, 1.10× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: decisions/providers.py src/flock/decisions/providers.py— FileTooLong — 529 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 29 over it, 1.06× 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: REDACTED REDACTED— FileTooLong — 528 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 28 over it, 1.06× 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: services/indexeddb.ts src/flock/frontend/src/services/indexeddb.ts— FileTooLong — 503 significant lines (blank, comment-only and punctuation-only lines excluded), about 83% of them inside a single declaration: IndexedDBService (149-845). The bar is 500 significant lines; this is 3 over it, 1.01× 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.
X2 · Cancellation propagation· Async function without AbortSignal · ×17
Async function without AbortSignal: fetchRunHistory src/flock/frontend/src/components/details/RunStatusTab.tsx:29— `fetchRunHistory` 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: fetchMessageHistory src/flock/frontend/src/components/details/MessageHistoryTab.tsx:36— `fetchMessageHistory` 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: fetchHistory src/flock/frontend/src/components/details/LiveOutputTab.tsx:24— `fetchHistory` 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: fetchTraces src/flock/frontend/src/components/modules/TraceModuleJaeger.tsx:142— `fetchTraces` 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: loadTraceServices src/flock/frontend/src/components/settings/TracingSettings.tsx:56— `loadTraceServices` 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: loadTraceStats src/flock/frontend/src/components/settings/TracingSettings.tsx:68— `loadTraceStats` 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: fetchVersion src/flock/frontend/src/components/settings/AdvancedSettings.tsx:33— `fetchVersion` 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: fetchThemeList src/flock/frontend/src/services/themeService.ts:15— `fetchThemeList` 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: fetchTheme src/flock/frontend/src/services/themeService.ts:39— `fetchTheme` 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: fetchArtifactTypes src/flock/frontend/src/services/api.ts:120— `fetchArtifactTypes` 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: fetchAgents src/flock/frontend/src/services/api.ts:150— `fetchAgents` 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: publishArtifact src/flock/frontend/src/services/api.ts:187— `publishArtifact` 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: reviewDecision src/flock/frontend/src/services/api.ts:232— `reviewDecision` 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: invokeAgent src/flock/frontend/src/services/api.ts:253— `invokeAgent` 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: fetchArtifact src/flock/frontend/src/services/api.ts:316— `fetchArtifact` 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: fetchArtifacts src/flock/frontend/src/services/api.ts:331— `fetchArtifacts` 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: fetchArtifactSummary src/flock/frontend/src/services/api.ts:360— `fetchArtifactSummary` 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 })`.
Repeated repair: src/flock/core/image.py src/flock/core/image.py:194— src/flock/core/image.py changed 11 times in last 90 days and 9 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is image.check_inline_images at line 194), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: embedded models are checked by their field values, not model_dump() (#513)”; “fix: extra base64 padding cannot shrink the image size estimate (#513)”; “fix: the store-side image check enforces only the limits (#513)”; “fix: image check covers embedded models and containers under url; accurate upload timing (#513)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-17..2026-10-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-17 15:22:17 +02:00' --until='2026-10-15 15:22:17 +02:00' --full-history --no-merges -- src/flock/core/image.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/flock/api/collector.py src/flock/api/collector.py:170— src/flock/api/collector.py changed 13 times in last 90 days and 7 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 12 (its worst body is DashboardEventCollector.on_pre_consume at line 170), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: an agent's last error is the failure the collector saw last, not the latest timestamp (#585)”; “fix: agent status per agent in O(1), ordered by creation, and carried by the run events (#585)”; “fix: agent status follows its runs, also when they end out of order; counted subscriptions keep their count (#585)”; “fix: run durations use the monotonic clock; Run Status shows active runs without a duration (#571)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-17..2026-10-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-17 15:22:17 +02:00' --until='2026-10-15 15:22:17 +02:00' --full-history --no-merges -- src/flock/api/collector.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/flock/core/store.py src/flock/core/store.py:137— src/flock/core/store.py changed 9 times in last 90 days and 7 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is BlackboardStore.consumptions_of at line 137), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: an artifact's history is read by its ID in every store (#605)”; “fix: a histogram range too wide for exact 64-bit buckets is rejected (#572)”; “fix: histogram buckets in whole microseconds in every store; errors count by their resolved type (#572)”; “fix: models with field aliases work everywhere: payloads are rebuilt from field names too (#544)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-17..2026-10-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-17 15:22:17 +02:00' --until='2026-10-15 15:22:17 +02:00' --full-history --no-merges -- src/flock/core/store.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/flock/components/server/traces/trace_component.py src/flock/components/server/traces/trace_component.py:61— src/flock/components/server/traces/trace_component.py changed 11 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is trace_component._span_from_row at line 61), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: one trace flush at a time, no clear before it finished (#601)”; “fix: dashboard trace reads connect like the tracer's exporter (#599)”; “fix: agent traces for names with a slash, off the event loop, with literal SQL (#597)”; “fix: the dashboard reads the trace file the tracer writes (#594)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-17..2026-10-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-17 15:22:17 +02:00' --until='2026-10-15 15:22:17 +02:00' --full-history --no-merges -- src/flock/components/server/traces/trace_component.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/flock/engines/dspy/image_inputs.py src/flock/engines/dspy/image_inputs.py:76— src/flock/engines/dspy/image_inputs.py changed 6 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is image_inputs.dspy_input_model at line 76), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: models with field aliases work everywhere: payloads are rebuilt from field names too (#544)”; “fix(dspy): a computed Image field is sent as an image too (#510)”; “fix(dspy): keep computed fields in image copies; check the model before scanning (#510)”; “fix(dspy): vision check inspects the DSPy input copy that is sent (#510)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-17..2026-10-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-17 15:22:17 +02:00' --until='2026-10-15 15:22:17 +02:00' --full-history --no-merges -- src/flock/engines/dspy/image_inputs.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/flock/api/thumbnails.py src/flock/api/thumbnails.py:46— src/flock/api/thumbnails.py changed 5 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is thumbnails._locate_images at line 46), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: image key segments match the JSON keys of the payload (#512)”; “fix: image-like values never fail thumbnails; image modal on the modal layer (#512)”; “fix: exact image sizes, stable thumbnail identity, documented keys (#512)”; “fix: thumbnails off the event loop, key segments, modal overlay, isolated tests (#512)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-17..2026-10-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-17 15:22:17 +02:00' --until='2026-10-15 15:22:17 +02:00' --full-history --no-merges -- src/flock/api/thumbnails.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/flock/api/service.py src/flock/api/service.py:62— src/flock/api/service.py changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 1 (its worst body is BlackboardHTTPService.__init__ at line 62), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: a run's webhook numbers survive eviction, the limit holds on insert (#618)”; “fix: named runs keep their webhook sequence and their status route (#618)”; “fix: requests continue the caller's trace at the agents level (#601)”; “fix(api): carry the REST correlation id on the artifact; tolerate consumptions without one; apply external log level to dspy/litellm”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-17..2026-10-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-17 15:22:17 +02:00' --until='2026-10-15 15:22:17 +02:00' --full-history --no-merges -- src/flock/api/service.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/flock/cli.py src/flock/cli.py:182— src/flock/cli.py changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is cli.decisions_calibrate at line 182), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: decisions record the decider's mode, so escalating or voting deciders get no suggestion even without an escalation or vote; the CLI prints thresholds exactly (#542)”; “fix: honest recall in the calibration example; no suggestions for escalating or voting deciders; decisions record item thresholds; one threshold per item; accessible threshold list (#542)”; “fix: the calibrate CLI finds persisted decisions of unimported types, rejects a zero target; dotted item ids keep their dots (#542)”; “fix: calibration labels per question, grouped per decider, checked bounds; item thresholds can name their checklist (#542)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-17..2026-10-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-17 15:22:17 +02:00' --until='2026-10-15 15:22:17 +02:00' --full-history --no-merges -- src/flock/cli.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/flock/decisions/coverage.py src/flock/decisions/coverage.py:96— src/flock/decisions/coverage.py changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is coverage.combine_results at line 96), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: explicit coverage visibility covers decisions about subjects with mixed visibilities (#536)”; “fix: coverage skips history without its subject; direct-only subscriptions cannot aggregate (#536)”; “fix: coverage history counts only decisions the subscriptions receive; callable keys accept alias-only models; no sort per agent (#536)”; “fix: coverages carry a revision; the highest per group is current (#536)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-17..2026-10-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-17 15:22:17 +02:00' --until='2026-10-15 15:22:17 +02:00' --full-history --no-merges -- src/flock/decisions/coverage.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/flock/decisions/explain.py src/flock/decisions/explain.py:104— src/flock/decisions/explain.py changed 4 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is explain.decision_case at line 104), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: explanations use the question text actually asked; only handles after .explains(); docs describe the more button (#534)”; “fix: every decision of an AND handle reaches the explainer; batch guard in both call orders; expandable explanation note (#534)”; “fix: explains(visibility=) for mixed subjects, checked before the LLM; no batch subscriptions (#534)”; “fix: explanations show only evaluated candidates and refused items; no explanation without a decision (#534)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-17..2026-10-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-17 15:22:17 +02:00' --until='2026-10-15 15:22:17 +02:00' --full-history --no-merges -- src/flock/decisions/explain.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/flock/api/image_uploads.py src/flock/api/image_uploads.py:51— src/flock/api/image_uploads.py changed 4 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is image_uploads.image_slot at line 51), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: server re-encodes dashboard images; robust upload parsing and pending state (#511)”; “fix: one count per aliased field; publishing waits for picture conversions (#511)”; “fix: alias keys for uploads, late picture conversions, transparent WebP (#511)”; “fix: bound upload requests, accept field aliases, keep list defaults (#511)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-17..2026-10-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-17 15:22:17 +02:00' --until='2026-10-15 15:22:17 +02:00' --full-history --no-merges -- src/flock/api/image_uploads.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/flock/orchestrator/artifact_manager.py src/flock/orchestrator/artifact_manager.py:107— src/flock/orchestrator/artifact_manager.py changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 13 (its worst body is ArtifactManager.publish at line 107), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: check inline images before every store write, also with sibling keys (#513)”; “fix(orchestrator): validate dict publishes against the registered model”; “fix(orchestrator): resolve simple type names on dict publish; harden Dapr example stacks”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-17..2026-10-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-17 15:22:17 +02:00' --until='2026-10-15 15:22:17 +02:00' --full-history --no-merges -- src/flock/orchestrator/artifact_manager.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/flock/frontend/src/utils/imageFields.ts src/flock/frontend/src/utils/imageFields.ts:28— src/flock/frontend/src/utils/imageFields.ts changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is imageFields.imageFieldKind at line 28), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: thumbnails off the event loop, key segments, modal overlay, isolated tests (#512)”; “fix: server re-encodes dashboard images; robust upload parsing and pending state (#511)”; “fix: alias keys for uploads, late picture conversions, transparent WebP (#511)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-17..2026-10-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-17 15:22:17 +02:00' --until='2026-10-15 15:22:17 +02:00' --full-history --no-merges -- src/flock/frontend/src/utils/imageFields.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/flock/application/application.py src/flock/application/application.py:834— src/flock/application/application.py changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 14 (its worst body is FlockApplication._check_contract at line 834), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: FlockApplication accepts alias inputs given as another model or by field name (#544)”; “fix: models with field aliases work everywhere: payloads are rebuilt from field names too (#544)”; “fix: address review findings (shutdown gate, init lock, start-up cancellation, sample build)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-17..2026-10-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-17 15:22:17 +02:00' --until='2026-10-15 15:22:17 +02:00' --full-history --no-merges -- src/flock/application/application.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/flock/decisions/review.py src/flock/decisions/review.py:24— src/flock/decisions/review.py changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is review.review_decision at line 24), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: an unknown decision id is a LookupError whatever the reviewer's name (#540)”; “fix: a late review keeps the decision's end of embargo; refused decisions offer their options for review (#540)”; “fix: reviewers cannot take an agent's name; a dashboard review refreshes the graph (#540)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-17..2026-10-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-17 15:22:17 +02:00' --until='2026-10-15 15:22:17 +02:00' --full-history --no-merges -- src/flock/decisions/review.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/flock/decisions/sections.py src/flock/decisions/sections.py:35— src/flock/decisions/sections.py changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is sections._paragraphs at line 35), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: paragraphs lose their surrounding whitespace, so no empty section; the request bound is per pass (#538)”; “fix: section splits skip whole separator runs; split_sections rejects non-positive limits (#538)”; “fix: bounded section requests and max_sections; a refused section keeps an item from no; no empty trailing section (#538)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-17..2026-10-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-17 15:22:17 +02:00' --until='2026-10-15 15:22:17 +02:00' --full-history --no-merges -- src/flock/decisions/sections.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
TodoComment src/flock/components/server/agents/agents_component.py:90— # TODO: relevant for MCP-component in the future — 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 src/flock/components/server/agents/agents_component.py:187— # TODO: relevant for MCP-Component in the future — 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 src/flock/components/server/traces/trace_component.py:97— # TODO: Add option for remote tracing DB-Path — 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 src/flock/frontend/src/components/modules/ModuleRegistry.ts:6— // TODO: Update module system to use GraphNode[] instead of Maps — 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 src/flock/frontend/src/components/settings/TracingSettings.tsx:80— // TODO: Load current .env settings from backend — 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 src/flock/frontend/src/components/settings/TracingSettings.tsx:125— // TODO: Implement backend endpoint to save to .env — 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 src/flock/frontend/src/services/indexeddb.test.ts:582— // TODO: Refactor to test in-memory fallback separately — 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 src/flock/integrations/openclaw/config.py:18— # TODO(phase2): widen to Literal["spawn", "session"] once session mode lands. — 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 src/flock/mcp/client.py:626— # TODO: get_session_id_callback is currently ignored. — 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 src/flock/orchestrator/correlation_engine.py:164— # TODO: Log warning? — 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 tests/test_orchestrator_combined.py:930— # TODO (Phase 4 Completion): Update documentation — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
Duplicated block (11 lines × 2) src/flock/components/agent/guard.py:172— src/flock/components/agent/guard.py:172-182 | src/flock/components/agent/guard.py:203-213 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (11 lines × 2) src/flock/core/store.py:334— src/flock/core/store.py:334-344 | src/flock/storage/dapr/dapr_state_blackboard_store.py:1091-1101 — 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) src/flock/api/graph_builder.py:611— src/flock/api/graph_builder.py:611-621 | src/flock/components/agent/output_utility.py:143-153 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: the declarations holding them bind `agent` to `object` in one and `"Agent"` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (11 lines × 2) src/flock/logging/formatters/theme_builder.py:192— src/flock/logging/formatters/theme_builder.py:192-202 | src/flock/logging/formatters/themed_formatter.py:189-206 — before extracting anything, compare `src/flock/logging/formatters/theme_builder.py` and `src/flock/logging/formatters/themed_formatter.py` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 213 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. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (11 lines × 2) examples/05-engines/01_adapter_comparison.py:122— examples/05-engines/01_adapter_comparison.py:122-132 | examples/05-engines/01_adapter_comparison.py:138-148 — 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) examples/15-decisions/04_question_types.py:202— examples/15-decisions/04_question_types.py:202-212 | examples/15-decisions/10_explain.py:165-175 — 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) examples/15-decisions/05_compliance_checklist.py:211— examples/15-decisions/05_compliance_checklist.py:211-221 | examples/15-decisions/11_coverage.py:163-173 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (11 lines × 2) examples/15-decisions/08_voting.py:175— examples/15-decisions/08_voting.py:175-185 | examples/15-decisions/09_shadow.py:177-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 (13 lines × 2 locations) src/flock/frontend/src/components/controls/PublishControl.tsx:526— src/flock/frontend/src/components/controls/PublishControl.tsx:526 · src/flock/frontend/src/components/controls/PublishControl.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.
Duplicated block (13 lines × 2 locations) src/flock/frontend/src/components/graph/AgentNode.tsx:247— src/flock/frontend/src/components/graph/AgentNode.tsx:247 · src/flock/frontend/src/components/graph/AgentNode.tsx:310 — 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) src/flock/frontend/src/components/graph/DecisionDisplay.tsx:379— src/flock/frontend/src/components/graph/DecisionDisplay.tsx:379 · src/flock/frontend/src/components/graph/DecisionDisplay.tsx:773 — 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) src/flock/frontend/src/components/settings/TracingSettings.tsx:258— src/flock/frontend/src/components/settings/TracingSettings.tsx:258 · src/flock/frontend/src/components/settings/TracingSettings.tsx:274 — 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 locations) src/flock/frontend/src/services/api.ts:331— src/flock/frontend/src/services/api.ts:331 · src/flock/frontend/src/services/api.ts:360 — 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) src/flock/frontend/src/services/layout.ts:167— src/flock/frontend/src/services/layout.ts:167 · src/flock/frontend/src/services/layout.ts:264 — 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.
ClassTooLong: TraceModuleJaeger src/flock/frontend/src/components/modules/TraceModuleJaeger.tsx:1— ClassTooLong — 1223 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 823 over it, 3.06× 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: GraphCanvas src/flock/frontend/src/components/graph/GraphCanvas.tsx:1— ClassTooLong — 553 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 153 over it, 1.38× 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: PublishControl src/flock/frontend/src/components/controls/PublishControl.tsx:1— ClassTooLong — 534 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 134 over it, 1.34× 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: WebSocketClient src/flock/frontend/src/services/websocket.ts:13— ClassTooLong — 423 significant lines (blank, comment-only and punctuation-only lines excluded), 21 methods. The bar is 400 significant lines; this is 23 over it, 1.06× 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: IndexedDBService src/flock/frontend/src/services/indexeddb.ts:149— ClassTooLong — 415 significant lines (blank, comment-only and punctuation-only lines excluded), 30 methods. The bar is 400 significant lines; this is 15 over it, 1.04× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Duplicated block (13 lines × 2) src/flock/engines/dspy/signature_builder.py:244— src/flock/engines/dspy/signature_builder.py:244-256 | src/flock/engines/dspy/signature_builder.py:402-414 — 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) src/flock/engines/dspy/signature_builder.py:286— src/flock/engines/dspy/signature_builder.py:286-298 | src/flock/engines/dspy/signature_builder.py:460-472 — 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) src/flock/engines/dspy/streaming_executor.py:287— src/flock/engines/dspy/streaming_executor.py:287-299 | src/flock/engines/dspy/streaming_executor.py:557-569 — 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) src/flock/mcp/servers/sse/flock_sse_server.py:70— src/flock/mcp/servers/sse/flock_sse_server.py:70-82 | src/flock/mcp/servers/streamable_http/flock_streamable_http_server.py:79-91 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (13 lines × 2) src/flock/storage/dapr/dapr_state_blackboard_store.py:739— src/flock/storage/dapr/dapr_state_blackboard_store.py:739-751 | src/flock/storage/dapr/dapr_state_blackboard_store.py:782-794 — 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) src/flock/components/server/agents/agents_component.py:74— src/flock/components/server/agents/agents_component.py:74-82 | src/flock/components/server/artifacts/artifacts_component.py:156-164 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) src/flock/decisions/providers.py:563— src/flock/decisions/providers.py:563-571 | src/flock/decisions/providers.py:669-677 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/flock/decisions/providers.py:563` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) examples/15-decisions/10_explain.py:128— examples/15-decisions/10_explain.py:128-136 | examples/15-decisions/13_human_review.py:138-146 — 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) examples/15-decisions/11_coverage.py:98— examples/15-decisions/11_coverage.py:98-106 | examples/15-decisions/12_long_documents.py:97-105 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `examples/15-decisions/12_long_documents.py:109` calls `manuals` and `examples/15-decisions/11_coverage.py:110` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 2) examples/15-decisions/05_compliance_checklist.py:139— examples/15-decisions/05_compliance_checklist.py:139-147 | examples/15-decisions/11_coverage.py:85-93 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
R4 · Test Coverage· No test reaches this file · ×5
No test reaches this file src/flock/frontend/src/components/common/EmptyState.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/flock/frontend/src/utils/mockData.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/flock/frontend/src/components/common/LoadingSpinner.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/flock/frontend/src/utils/artifacts.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/flock/frontend/src/main.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
X17 · Uncapped recursion over a caller-supplied document· Recursive walk over a caller-supplied document has no depth cap · ×5
Recursive walk over a caller-supplied document has no depth cap src/flock/api/thumbnails.py:55— `find_images` is public, takes a document from its caller (line 73) and hands it to `_locate_images`, which calls itself at line 55 (`_locate_images`) with a piece of `value` (and at line 58) — and nowhere in `_locate_images` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. Python's parsers accept far more nesting than its stack allows: `json.loads` turns 3,000 bytes of brackets into 1,500 levels and `xml.etree.ElementTree` parses tens of thousands, while a walk like this one raises `RecursionError` once it passes the interpreter's default limit of 1,000 frames. Wherever that exception lands, the work fails: a request errors, and outside any `try` the worker or the program exits with it. Raising `sys.setrecursionlimit` only moves the number the document has to beat. Thread a depth argument through `_locate_images` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap src/flock/api/thumbnails.py:89— `compact` is public and takes `value: Any` from its caller, and it calls itself at line 89 (`compact`) with a piece of `value` (and at line 91) — and nowhere in `compact` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. Python's parsers accept far more nesting than its stack allows: `json.loads` turns 3,000 bytes of brackets into 1,500 levels and `xml.etree.ElementTree` parses tens of thousands, while a walk like this one raises `RecursionError` once it passes the interpreter's default limit of 1,000 frames. Wherever that exception lands, the work fails: a request errors, and outside any `try` the worker or the program exits with it. Raising `sys.setrecursionlimit` only moves the number the document has to beat. Thread a depth argument through `compact` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap src/flock/core/image.py:216— `check_inline_images` is public and takes `value: Any` from its caller, and it calls itself at line 216 (`check_inline_images`) with a piece of `value` (and at line 219) — and nowhere in `check_inline_images` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. Python's parsers accept far more nesting than its stack allows: `json.loads` turns 3,000 bytes of brackets into 1,500 levels and `xml.etree.ElementTree` parses tens of thousands, while a walk like this one raises `RecursionError` once it passes the interpreter's default limit of 1,000 frames. Wherever that exception lands, the work fails: a request errors, and outside any `try` the worker or the program exits with it. Raising `sys.setrecursionlimit` only moves the number the document has to beat. Thread a depth argument through `check_inline_images` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap src/flock/frontend/src/utils/imageFields.ts:33— `imageFieldKind` is exported and takes `prop: any` from its caller, and it calls itself at line 33 (`imageFieldKind`) with a piece of `prop` — and nowhere in `imageFieldKind` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `imageFieldKind` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap src/flock/utils/visibility_utils.py:170— `deserialize_visibility` is public, takes a document from its caller (line 71) and hands it to `_validate_visibility`, which calls itself at line 170 (`_validate_visibility`) with a piece of `data` — and nowhere in `_validate_visibility` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. Python's parsers accept far more nesting than its stack allows: `json.loads` turns 3,000 bytes of brackets into 1,500 levels and `xml.etree.ElementTree` parses tens of thousands, while a walk like this one raises `RecursionError` once it passes the interpreter's default limit of 1,000 frames. Wherever that exception lands, the work fails: a request errors, and outside any `try` the worker or the program exits with it. Raising `sys.setrecursionlimit` only moves the number the document has to beat. Thread a depth argument through `_validate_visibility` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Swallowed exception (empty catch) scripts/generate_llm_codebase.py:224— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/flock/frontend/src/components/graph/LogicOperationsDisplay.tsx:85— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) src/flock/frontend/src/services/indexeddb.ts:264— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/flock/integrations/openclaw/streaming.py:484— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/flock/integrations/openclaw/engine.py:799— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
TooManyMethods: Flock src/flock/core/orchestrator.py:74— TooManyMethods — 51 methods. The bar is 30 methods; this is 21 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.
TooManyMethods: OpenClawEngine src/flock/integrations/openclaw/engine.py:33— 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.
TooManyMethods: GraphAssembler src/flock/api/graph_builder.py:65— TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: DaprStateBlackboardStore src/flock/storage/dapr/dapr_state_blackboard_store.py:260— TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Duplicated block (16 lines × 2 locations) src/flock/frontend/src/App.tsx:89— src/flock/frontend/src/App.tsx:89 · src/flock/frontend/src/components/modules/HistoricalArtifactsModule.tsx:105 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (16 lines × 2 locations) src/flock/frontend/src/components/details/MessageHistoryTab.tsx:298— src/flock/frontend/src/components/details/MessageHistoryTab.tsx:298 · src/flock/frontend/src/components/details/RunStatusTab.tsx:272 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (16 lines × 2 locations) src/flock/frontend/src/components/modules/JsonAttributeRenderer.tsx:46— src/flock/frontend/src/components/modules/JsonAttributeRenderer.tsx:46 · src/flock/frontend/src/components/modules/JsonAttributeRenderer.tsx:67 — 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) src/flock/frontend/src/components/settings/TracingSettings.tsx:194— src/flock/frontend/src/components/settings/TracingSettings.tsx:194 · src/flock/frontend/src/components/settings/TracingSettings.tsx:213 — 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) src/flock/core/artifacts.py:48— src/flock/core/artifacts.py:48-57 | src/flock/core/visibility.py:77-86 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) examples/01-getting-started/05_mcp_and_tools.py:30— examples/01-getting-started/05_mcp_and_tools.py:30-39 | examples/01-getting-started/07_web_detective.py:28-37 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) examples/15-decisions/04_question_types.py:170— examples/15-decisions/04_question_types.py:170-179 | examples/15-decisions/10_explain.py:127-136 — 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 (22 lines × 2) src/flock/mcp/types/types.py:182— src/flock/mcp/types/types.py:182-203 | src/flock/mcp/types/types.py:269-290 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (22 lines × 2) examples/09-server-components/07_agents_component.py:117— examples/09-server-components/07_agents_component.py:117-138 | examples/09-server-components/08_control_routes_component.py:68-89 — before extracting anything, compare `examples/09-server-components/07_agents_component.py` and `examples/09-server-components/08_control_routes_component.py` as WHOLE FILES: this scan already matched 3 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `examples/09-server-components/07_agents_component.py:117` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16–19 lines × 2) src/flock/orchestrator/server_manager.py:256— src/flock/orchestrator/server_manager.py:256-274 | src/flock/orchestrator/server_manager.py:372-387 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/flock/orchestrator/server_manager.py:256` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16–19 lines × 2) examples/01-getting-started/15_iot_sensor_batching.py:118— examples/01-getting-started/15_iot_sensor_batching.py:118-136 | examples/01-getting-started/15_iot_sensor_batching.py:141-156 — 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) src/flock/logging/formatters/theme_builder.py:233— src/flock/logging/formatters/theme_builder.py:233-248 | src/flock/logging/formatters/themed_formatter.py:245-264 — before extracting anything, compare `src/flock/logging/formatters/theme_builder.py` and `src/flock/logging/formatters/themed_formatter.py` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 213 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/flock/logging/formatters/theme_builder.py:233` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) src/flock/storage/dapr/dapr_state_blackboard_store.py:984— src/flock/storage/dapr/dapr_state_blackboard_store.py:984-999 | src/flock/storage/dapr/dapr_state_blackboard_store.py:1012-1027 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/flock/storage/dapr/dapr_state_blackboard_store.py:984` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) src/flock/api/graph_builder.py:798— src/flock/api/graph_builder.py:798-805 | src/flock/api/graph_builder.py:1095-1102 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/flock/api/graph_builder.py:798` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) src/flock/components/server/agents/agents_component.py:55— src/flock/components/server/agents/agents_component.py:55-62 | src/flock/components/server/artifacts/artifacts_component.py:137-144 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 2) src/flock/orchestrator/artifact_manager.py:60— src/flock/orchestrator/artifact_manager.py:60-76 | src/flock/orchestrator/scheduler.py:223-234 — 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `listener` to `PublicationListener` in one and `TaskOutcomeListener` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (12 lines × 2) examples/09-server-components/01_authentication_component.py:128— examples/09-server-components/01_authentication_component.py:128-141 | examples/09-server-components/12_complete_composition.py:84-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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (25 lines × 2 locations) src/flock/frontend/src/components/details/MessageHistoryTab.tsx:210— src/flock/frontend/src/components/details/MessageHistoryTab.tsx:210 · src/flock/frontend/src/components/details/RunStatusTab.tsx:174 — the 2 copies are spread across 2 files, and what repeats is a LIST OF ENTRIES rather than behaviour — the same entries written out more than once. Extract them into one shared, exported constant and spread that constant into each site, rather than into a function the sites call: a list like this often lives in declarative metadata (a decorator's options object, a static configuration table) that a build step must be able to read statically, where a function call is not allowed. Adding an entry to one copy and not the other is the failure this prevents.
Duplicated block (25 lines × 2 locations) src/flock/frontend/src/components/settings/ThemeSelector.tsx:204— src/flock/frontend/src/components/settings/ThemeSelector.tsx:204 · src/flock/frontend/src/components/settings/ThemeSelector.tsx:244 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (23 lines × 2 locations) src/flock/frontend/src/components/controls/PublishControl.tsx:472— src/flock/frontend/src/components/controls/PublishControl.tsx:472 · src/flock/frontend/src/components/controls/PublishControl.tsx:499 — 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 (23 lines × 2 locations) src/flock/frontend/src/services/layout.ts:390— src/flock/frontend/src/services/layout.ts:390 · src/flock/frontend/src/services/layout.ts:503 — 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) src/flock/frontend/src/components/details/MessageHistoryTab.tsx:49— src/flock/frontend/src/components/details/MessageHistoryTab.tsx:49 · src/flock/frontend/src/components/details/MessageHistoryTab.tsx:96 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2 locations) src/flock/frontend/src/components/layout/DashboardLayout.tsx:143— src/flock/frontend/src/components/layout/DashboardLayout.tsx:143 · src/flock/frontend/src/components/layout/DashboardLayout.tsx:164 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 4 locations) src/flock/frontend/src/services/api.ts:122— src/flock/frontend/src/services/api.ts:122 · src/flock/frontend/src/services/api.ts:152 · src/flock/frontend/src/services/api.ts:335 · src/flock/frontend/src/services/api.ts:364 — 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 (15 lines × 4 locations) src/flock/frontend/src/services/indexeddb.ts:556— src/flock/frontend/src/services/indexeddb.ts:556 · src/flock/frontend/src/services/indexeddb.ts:606 · src/flock/frontend/src/services/indexeddb.ts:656 · src/flock/frontend/src/services/indexeddb.ts:706 — 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 (14 lines × 2 locations) src/flock/frontend/src/components/controls/PublishControl.tsx:632— src/flock/frontend/src/components/controls/PublishControl.tsx:632 · src/flock/frontend/src/components/settings/SettingsPanel.tsx:46 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (14 lines × 2 locations) src/flock/frontend/src/components/settings/AppearanceSettings.tsx:16— src/flock/frontend/src/components/settings/AppearanceSettings.tsx:16 · src/flock/frontend/src/components/settings/GraphSettings.tsx:14 — 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.
AC4 · Keyboard semantics· Modal dialog does not manage focus · ×1
Modal dialog does not manage focus src/flock/frontend/src/components/filters/FilterFlyout.tsx:17— This <aside role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
AC7 · A11y enforcement· Accessibility enforcement below the top rung · ×1
Accessibility enforcement below the top rung — 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 53 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.
AgentBuilder.decides (cyclomatic 66) src/flock/core/agent.py:803— AgentBuilder.decides has cyclomatic complexity 66 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AgentNode.AgentNode (cyclomatic 65) src/flock/frontend/src/components/graph/AgentNode.tsx:12— AgentNode.AgentNode has cyclomatic complexity 65 (threshold 15). Of this number, 38 points are the body's own statements and 27 belong to 9 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.
LogicOperationsDisplay.LogicOperationsDisplay (cyclomatic 55) src/flock/frontend/src/components/graph/LogicOperationsDisplay.tsx:25— LogicOperationsDisplay.LogicOperationsDisplay has cyclomatic complexity 55 (threshold 15). Most of this is not in the body itself: 4 of the 55 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 116, a function literal at line 131, a function literal at line 323, …). 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.
PublishControl.PublishControl::renderField (cyclomatic 54) src/flock/frontend/src/components/controls/PublishControl.tsx:320— PublishControl.PublishControl::renderField has cyclomatic complexity 54 (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.
HistoricalArtifactsModule.HistoricalArtifactsModule (cyclomatic 52) src/flock/frontend/src/components/modules/HistoricalArtifactsModule.tsx:41— HistoricalArtifactsModule.HistoricalArtifactsModule has cyclomatic complexity 52 (threshold 15). Of this number, 23 points are the body's own statements and 29 belong to 15 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
GraphAssembler._build_agent_nodes (cyclomatic 47) src/flock/api/graph_builder.py:322— GraphAssembler._build_agent_nodes has cyclomatic complexity 47 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DecisionDisplay.DecisionBars (cyclomatic 40) src/flock/frontend/src/components/graph/DecisionDisplay.tsx:1254— DecisionDisplay.DecisionBars has cyclomatic complexity 40 (threshold 15). Of this number, 39 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TraceModuleJaeger.TraceModuleJaeger (cyclomatic 38) src/flock/frontend/src/components/modules/TraceModuleJaeger.tsx:73— TraceModuleJaeger.TraceModuleJaeger has cyclomatic complexity 38 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (TraceModuleJaeger.TraceModuleJaeger::renderSpanNode) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
GraphCanvas.GraphCanvas (cyclomatic 35) src/flock/frontend/src/components/graph/GraphCanvas.tsx:44— GraphCanvas.GraphCanvas has cyclomatic complexity 35 (threshold 15). Most of this is not in the body itself: 10 of the 35 points are its own statements and the rest belongs to 11 function literals inside it that branch (lines 196, 291, 178, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
OpenClawEngine.evaluate (cyclomatic 33) src/flock/integrations/openclaw/engine.py:106— OpenClawEngine.evaluate has cyclomatic complexity 33 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
WebSocketClient.updateFilterStateFromPublishedMessage (cyclomatic 33) src/flock/frontend/src/services/websocket.ts:63— WebSocketClient.updateFilterStateFromPublishedMessage has cyclomatic complexity 33 (threshold 15). Of this number, 31 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
useKeyboardShortcuts.useKeyboardShortcuts (cyclomatic 33) src/flock/frontend/src/hooks/useKeyboardShortcuts.ts:26— useKeyboardShortcuts.useKeyboardShortcuts has cyclomatic complexity 33 (threshold 15). Most of this is not in the body itself: 1 of the 33 points is its own statement and the rest belongs to one function literal inside it that branches (line 28). 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.
DecisionEngine._checklist_decision (cyclomatic 30) src/flock/decisions/engine.py:892— DecisionEngine._checklist_decision has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DSPyEngine._evaluate_internal (cyclomatic 29) REDACTED:386— DSPyEngine._evaluate_internal has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TournamentBracket.TournamentBracket (cyclomatic 28) src/flock/frontend/src/components/graph/TournamentBracket.tsx:95— TournamentBracket.TournamentBracket has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 2 of the 28 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 284, a function literal at line 263, a function literal at line 113, …). 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.
DSPySignatureBuilder.prepare_signature_for_output_group (cyclomatic 27) src/flock/engines/dspy/signature_builder.py:175— DSPySignatureBuilder.prepare_signature_for_output_group has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
OpenClawEngine._build_responses_payload (cyclomatic 27) src/flock/integrations/openclaw/engine.py:579— OpenClawEngine._build_responses_payload has cyclomatic complexity 27 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
MultiSelect.MultiSelect (cyclomatic 27) src/flock/frontend/src/components/settings/MultiSelect.tsx:21— MultiSelect.MultiSelect has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 9 of the 27 points are its own statements and the rest belongs to 7 function items inside it that branch (handleKeyDown, a function literal at line 43, a function literal at line 212, …). 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.
OutputProcessor.make_outputs_for_group (cyclomatic 26) src/flock/agent/output_processor.py:46— OutputProcessor.make_outputs_for_group has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AgentBuilder.consumes (cyclomatic 26) src/flock/core/agent.py:581— AgentBuilder.consumes has cyclomatic complexity 26 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
WebSocketClient.setupEventHandlers (cyclomatic 26) src/flock/frontend/src/services/websocket.ts:166— WebSocketClient.setupEventHandlers has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 1 of the 26 points is its own statement and the rest belongs to 7 function literals inside it that branch (lines 219, 182, 261, …). 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.
DecisionEngine.evaluate (cyclomatic 25) src/flock/decisions/engine.py:261— DecisionEngine.evaluate has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MessageHistoryTab.MessageHistoryTab (cyclomatic 25) src/flock/frontend/src/components/details/MessageHistoryTab.tsx:23— MessageHistoryTab.MessageHistoryTab has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 4 of the 25 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 280, a function literal at line 36, a function literal at line 84, …). 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.
ThemeSelector.ThemeSelector (cyclomatic 25) src/flock/frontend/src/components/settings/ThemeSelector.tsx:14— ThemeSelector.ThemeSelector has cyclomatic complexity 25 (threshold 15). Of this number, 15 points are the body's own statements and 10 belong to 6 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
TracingSettings.TracingSettings (cyclomatic 25) src/flock/frontend/src/components/settings/TracingSettings.tsx:30— TracingSettings.TracingSettings has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 10 of the 25 points are its own statements and the rest belongs to 7 function items inside it that branch (handleClearTraces, loadTraceServices, loadTraceStats, …). 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.
OutputUtilityComponent.on_post_evaluate (cyclomatic 24) src/flock/components/agent/output_utility.py:174— OutputUtilityComponent.on_post_evaluate has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
RunStatusTab.RunStatusTab (cyclomatic 24) src/flock/frontend/src/components/details/RunStatusTab.tsx:22— RunStatusTab.RunStatusTab has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 4 of the 24 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 244, a function literal at line 29, 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.
layout.resolveNodeOverlaps (cyclomatic 23) src/flock/frontend/src/services/layout.ts:147— layout.resolveNodeOverlaps has cyclomatic complexity 23 (threshold 15). Of this number, 21 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
calibration.calibrate (cyclomatic 22) src/flock/decisions/calibration.py:96— calibration.calibrate has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_QuestionMeta.__new__ (cyclomatic 22) src/flock/decisions/choice.py:144— _QuestionMeta.__new__ has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ScheduledAgentDisplay.ScheduledAgentDisplay::formatScheduleDetails (cyclomatic 21) src/flock/frontend/src/components/graph/ScheduledAgentDisplay.tsx:78— ScheduledAgentDisplay.ScheduledAgentDisplay::formatScheduleDetails has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
WebSocketClient.connect (cyclomatic 21) src/flock/frontend/src/services/websocket.ts:392— WebSocketClient.connect has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 10 of the 21 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 457, 406, 421, …). 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.
SavedFiltersControl.SavedFiltersControl (cyclomatic 21) src/flock/frontend/src/components/filters/SavedFiltersControl.tsx:6— SavedFiltersControl.SavedFiltersControl has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 5 of the 21 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 31, handleSavePreset, handleApplyPreset, …). 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.
TimerComponent._timer_loop (cyclomatic 20) src/flock/components/orchestrator/scheduling/timer.py:123— TimerComponent._timer_loop has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
graph.decision_view (cyclomatic 20) src/flock/decisions/graph.py:174— graph.decision_view has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
WebSocketClient.handleMessage (cyclomatic 20) src/flock/frontend/src/services/websocket.ts:511— WebSocketClient.handleMessage has cyclomatic complexity 20 (threshold 15). Of this number, 19 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
MessageDetailWindow.MessageDetailWindow (cyclomatic 20) src/flock/frontend/src/components/details/MessageDetailWindow.tsx:12— MessageDetailWindow.MessageDetailWindow has cyclomatic complexity 20 (threshold 15). Of this number, 16 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DashboardLayout.DashboardLayout (cyclomatic 20) src/flock/frontend/src/components/layout/DashboardLayout.tsx:21— DashboardLayout.DashboardLayout has cyclomatic complexity 20 (threshold 15). Of this number, 17 points are the body's own statements and 3 belong to 3 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
graph._question_info (cyclomatic 19) src/flock/decisions/graph.py:29— graph._question_info has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
App.App (cyclomatic 19) src/flock/frontend/src/App.tsx:16— App.App has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to 6 function literals inside it that branch (lines 19, 67, 89, …). 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.
DSPyArtifactMaterializer.normalize_output_payload (cyclomatic 18) src/flock/engines/dspy/artifact_materializer.py:35— DSPyArtifactMaterializer.normalize_output_payload has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DSPyArtifactMaterializer.materialize_artifacts (cyclomatic 18) src/flock/engines/dspy/artifact_materializer.py:98— DSPyArtifactMaterializer.materialize_artifacts has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
trace_and_logged._serialize_value (cyclomatic 18) src/flock/logging/trace_and_logged.py:100— trace_and_logged._serialize_value has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
trace_and_logged._extract_span_attributes (cyclomatic 18) src/flock/logging/trace_and_logged.py:199— trace_and_logged._extract_span_attributes has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
LiveOutputTab.LiveOutputTab (cyclomatic 18) src/flock/frontend/src/components/details/LiveOutputTab.tsx:13— LiveOutputTab.LiveOutputTab has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 5 of the 18 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 24, 68, 87, …). 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.
TraceModuleJaeger.TraceModuleJaeger::renderSpanNode (cyclomatic 17) src/flock/frontend/src/components/modules/TraceModuleJaeger.tsx:501— TraceModuleJaeger.TraceModuleJaeger::renderSpanNode has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This shape REPEATS in the file: one other method here (TraceModuleJaeger.TraceModuleJaeger) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
GraphAssembler._build_logic_config_for_subscription (cyclomatic 16) src/flock/api/graph_builder.py:1256— GraphAssembler._build_logic_config_for_subscription has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
BuiltinCollectionComponent.on_collect_artifacts (cyclomatic 16) src/flock/components/orchestrator/collection.py:34— BuiltinCollectionComponent.on_collect_artifacts has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ArtifactsComponent._publish_upload (cyclomatic 16) src/flock/components/server/artifacts/artifacts_component.py:307— ArtifactsComponent._publish_upload has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
helpers._build_logic_config (cyclomatic 16) src/flock/components/server/control/helpers.py:245— helpers._build_logic_config has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Flock.get_correlation_status (cyclomatic 16) src/flock/core/orchestrator.py:362— Flock.get_correlation_status has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
FoundryResponsesAdapter._handle (cyclomatic 16) src/flock/integrations/foundry/adapter.py:217— FoundryResponsesAdapter._handle has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
FlockMCPClient.__init__ (cyclomatic 16) src/flock/mcp/client.py:231— FlockMCPClient.__init__ has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
extra.initKeyboardShortcuts (cyclomatic 16) docs/javascripts/extra.js:164— extra.initKeyboardShortcuts has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 3 of the 16 points are its own statements and the rest belongs to one function literal inside it that branches (line 165). 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.
MessageFlowEdge.MessageFlowEdge (cyclomatic 16) src/flock/frontend/src/components/graph/MessageFlowEdge.tsx:36— MessageFlowEdge.MessageFlowEdge has cyclomatic complexity 16 (threshold 15). Of this number, 12 points are the body's own statements and 4 belong to one function item inside it that branches. To reduce it, split the body: 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.
PendingJoinEdge.PendingJoinEdge (cyclomatic 16) src/flock/frontend/src/components/graph/PendingJoinEdge.tsx:38— PendingJoinEdge.PendingJoinEdge has cyclomatic complexity 16 (threshold 15). Of this number, 12 points are the body's own statements and 4 belong to one function item inside it that branches. To reduce it, 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.
NodeDetailWindow.NodeDetailWindow (cyclomatic 16) src/flock/frontend/src/components/details/NodeDetailWindow.tsx:13— NodeDetailWindow.NodeDetailWindow has cyclomatic complexity 16 (threshold 15). Of this number, 8 points are the body's own statements and 8 belong to 3 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
TraceModuleJaeger.TraceModuleJaeger (cognitive 124) src/flock/frontend/src/components/modules/TraceModuleJaeger.tsx:73— TraceModuleJaeger.TraceModuleJaeger has cognitive complexity 124 (threshold 15). Drivers by points: boolean chains 53, if/else 31 (44 pts), ternaries 22 (25 pts), error handling 1, match/switch 1 (nesting depth added 16). Of this number, 33 points are the body's own statements and 91 belong to 30 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
AgentBuilder.decides (cognitive 98) src/flock/core/agent.py:803— AgentBuilder.decides has cognitive complexity 98 (threshold 15). Drivers by points: if/else 40 (69 pts), boolean chains 17, loops 6 (10 pts), ternaries 2 (nesting depth added 33). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GraphAssembler._build_agent_nodes (cognitive 94) src/flock/api/graph_builder.py:322— GraphAssembler._build_agent_nodes has cognitive complexity 94 (threshold 15). Drivers by points: ternaries 21 (48 pts), if/else 14 (34 pts), boolean chains 7, loops 4 (5 pts) (nesting depth added 48). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
OpenClawEngine.evaluate (cognitive 70) src/flock/integrations/openclaw/engine.py:106— OpenClawEngine.evaluate has cognitive complexity 70 (threshold 15). Drivers by points: if/else 24 (53 pts), error handling 4 (10 pts), boolean chains 5, loops 1, ternaries 1 (nesting depth added 35). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OutputProcessor.make_outputs_for_group (cognitive 67) src/flock/agent/output_processor.py:46— OutputProcessor.make_outputs_for_group has cognitive complexity 67 (threshold 15). Drivers by points: if/else 15 (45 pts), loops 7 (21 pts), boolean chains 1 (nesting depth added 44). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PublishControl.PublishControl::renderField (cognitive 64) src/flock/frontend/src/components/controls/PublishControl.tsx:320— PublishControl.PublishControl::renderField has cognitive complexity 64 (threshold 15). Drivers by points: boolean chains 32, ternaries 12 (25 pts), if/else 7 (nesting depth added 13). 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.
layout.resolveNodeOverlaps (cognitive 56) src/flock/frontend/src/services/layout.ts:147— layout.resolveNodeOverlaps has cognitive complexity 56 (threshold 15). Drivers by points: ternaries 6 (26 pts), if/else 7 (19 pts), loops 3 (6 pts), boolean chains 5 (nesting depth added 35). Of this number, 53 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DSPySignatureBuilder.prepare_signature_for_output_group (cognitive 54) src/flock/engines/dspy/signature_builder.py:175— DSPySignatureBuilder.prepare_signature_for_output_group has cognitive complexity 54 (threshold 15). Drivers by points: if/else 20 (40 pts), boolean chains 5, loops 3 (5 pts), ternaries 1 (4 pts) (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AgentNode.AgentNode (cognitive 53) src/flock/frontend/src/components/graph/AgentNode.tsx:12— AgentNode.AgentNode has cognitive complexity 53 (threshold 15). Drivers by points: boolean chains 29, if/else 14 (16 pts), ternaries 8 (nesting depth added 2). Of this number, 32 points are the body's own statements and 21 belong to 9 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.
useKeyboardShortcuts.useKeyboardShortcuts (cognitive 46) src/flock/frontend/src/hooks/useKeyboardShortcuts.ts:26— useKeyboardShortcuts.useKeyboardShortcuts has cognitive complexity 46 (threshold 15). Drivers by points: if/else 22 (34 pts), boolean chains 9, ternaries 1 (3 pts) (nesting depth added 14). None of this is in the body itself: all 46 points belong to one function literal inside it that branches (line 28). 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.
DecisionEngine._checklist_decision (cognitive 42) src/flock/decisions/engine.py:892— DecisionEngine._checklist_decision has cognitive complexity 42 (threshold 15). Drivers by points: if/else 10 (14 pts), loops 7 (13 pts), boolean chains 9, ternaries 3 (6 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.
DecisionDisplay.DecisionBars (cognitive 42) src/flock/frontend/src/components/graph/DecisionDisplay.tsx:1254— DecisionDisplay.DecisionBars has cognitive complexity 42 (threshold 15). Drivers by points: ternaries 18 (28 pts), boolean chains 12, if/else 2 (nesting depth added 10). Of this number, 41 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MessageHistoryTab.MessageHistoryTab (cognitive 42) src/flock/frontend/src/components/details/MessageHistoryTab.tsx:23— MessageHistoryTab.MessageHistoryTab has cognitive complexity 42 (threshold 15). Drivers by points: ternaries 9 (28 pts), if/else 8, boolean chains 4, error handling 2 (nesting depth added 19). Most of this is not in the body itself: 6 of the 42 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 36, a function literal at line 280, a function literal at line 84, …). 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.
DecisionEngine.evaluate (cognitive 41) src/flock/decisions/engine.py:261— DecisionEngine.evaluate has cognitive complexity 41 (threshold 15). Drivers by points: if/else 14 (23 pts), ternaries 5 (10 pts), boolean chains 5, loops 2 (3 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DSPyEngine._evaluate_internal (cognitive 41) REDACTED:386— DSPyEngine._evaluate_internal has cognitive complexity 41 (threshold 15). Drivers by points: if/else 16 (23 pts), boolean chains 9, ternaries 5 (6 pts), error handling 2 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DSPyArtifactMaterializer.materialize_artifacts (cognitive 40) src/flock/engines/dspy/artifact_materializer.py:98— DSPyArtifactMaterializer.materialize_artifacts has cognitive complexity 40 (threshold 15). Drivers by points: if/else 8 (21 pts), error handling 3 (11 pts), loops 3 (7 pts), boolean chains 1 (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OpenClawEngine._build_responses_payload (cognitive 40) src/flock/integrations/openclaw/engine.py:579— OpenClawEngine._build_responses_payload has cognitive complexity 40 (threshold 15). Drivers by points: if/else 22 (29 pts), boolean chains 5, loops 2 (3 pts), ternaries 3 (nesting depth added 8). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
calibration.calibrate (cognitive 38) src/flock/decisions/calibration.py:96— calibration.calibrate has cognitive complexity 38 (threshold 15). Drivers by points: if/else 10 (23 pts), boolean chains 6, loops 3 (5 pts), ternaries 1 (4 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
HistoricalArtifactsModule.HistoricalArtifactsModule (cognitive 38) src/flock/frontend/src/components/modules/HistoricalArtifactsModule.tsx:41— HistoricalArtifactsModule.HistoricalArtifactsModule has cognitive complexity 38 (threshold 15). Drivers by points: boolean chains 19, if/else 14, ternaries 4, error handling 1. Most of this is not in the body itself: 14 of the 38 points are its own statements and the rest belongs to 15 function items inside it that branch (a function literal at line 230, a function literal at line 105, a function literal at line 197, …). 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.
OutputUtilityComponent.on_post_evaluate (cognitive 36) src/flock/components/agent/output_utility.py:174— OutputUtilityComponent.on_post_evaluate has cognitive complexity 36 (threshold 15). Drivers by points: if/else 16 (21 pts), loops 2 (6 pts), boolean chains 5, error handling 1 (2 pts), ternaries 1 (2 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DSPyArtifactMaterializer.normalize_output_payload (cognitive 35) src/flock/engines/dspy/artifact_materializer.py:35— DSPyArtifactMaterializer.normalize_output_payload has cognitive complexity 35 (threshold 15). Drivers by points: if/else 11 (25 pts), loops 2 (4 pts), boolean chains 3, error handling 1 (3 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ScheduledAgentDisplay.ScheduledAgentDisplay::formatScheduleDetails (cognitive 34) src/flock/frontend/src/components/graph/ScheduledAgentDisplay.tsx:78— ScheduledAgentDisplay.ScheduledAgentDisplay::formatScheduleDetails has cognitive complexity 34 (threshold 15). Drivers by points: ternaries 4 (14 pts), boolean chains 9, if/else 8 (9 pts), error handling 1 (2 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BuiltinCollectionComponent.on_collect_artifacts (cognitive 33) src/flock/components/orchestrator/collection.py:34— BuiltinCollectionComponent.on_collect_artifacts has cognitive complexity 33 (threshold 15). Drivers by points: if/else 14 (28 pts), loops 1 (3 pts), boolean chains 2 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AgentScheduler.schedule_artifact (cognitive 33) src/flock/orchestrator/scheduler.py:88— AgentScheduler.schedule_artifact has cognitive complexity 33 (threshold 15). Drivers by points: if/else 11 (29 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LogicOperationsDisplay.LogicOperationsDisplay (cognitive 32) src/flock/frontend/src/components/graph/LogicOperationsDisplay.tsx:25— LogicOperationsDisplay.LogicOperationsDisplay has cognitive complexity 32 (threshold 15). Drivers by points: boolean chains 21, if/else 9 (10 pts), error handling 1 (nesting depth added 1). Most of this is not in the body itself: 3 of the 32 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 116, calculateClientTime, a function literal at line 40, …). 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.
trace_and_logged._extract_span_attributes (cognitive 31) src/flock/logging/trace_and_logged.py:199— trace_and_logged._extract_span_attributes has cognitive complexity 31 (threshold 15). Drivers by points: if/else 10 (23 pts), error handling 2 (3 pts), loops 3, boolean chains 2 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MessageDetailWindow.MessageDetailWindow (cognitive 31) src/flock/frontend/src/components/details/MessageDetailWindow.tsx:12— MessageDetailWindow.MessageDetailWindow has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 7 (20 pts), boolean chains 8, if/else 2, error handling 1 (nesting depth added 13). Of this number, 26 points are the body's own statements and 5 belong to 2 function literals inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
App.App (cognitive 31) src/flock/frontend/src/App.tsx:16— App.App has cognitive complexity 31 (threshold 15). Drivers by points: if/else 14 (19 pts), ternaries 3 (8 pts), boolean chains 2, error handling 2 (nesting depth added 10). None of this is in the body itself: all 31 points belong to 6 function literals inside it that branch (lines 19, 67, 89, …). 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.
graph._question_info (cognitive 30) src/flock/decisions/graph.py:29— graph._question_info has cognitive complexity 30 (threshold 15). Drivers by points: if/else 12 (20 pts), boolean chains 4, loops 2 (4 pts), ternaries 1 (2 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TimerComponent._timer_loop (cognitive 29) src/flock/components/orchestrator/scheduling/timer.py:123— TimerComponent._timer_loop has cognitive complexity 29 (threshold 15). Drivers by points: if/else 11 (21 pts), boolean chains 4, error handling 2, loops 1, ternaries 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AgentBuilder.consumes (cognitive 29) src/flock/core/agent.py:581— AgentBuilder.consumes has cognitive complexity 29 (threshold 15). Drivers by points: if/else 15 (21 pts), boolean chains 7, ternaries 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Flock.run_until_idle (cognitive 29) src/flock/core/orchestrator.py:652— Flock.run_until_idle has cognitive complexity 29 (threshold 15). Drivers by points: if/else 11 (24 pts), loops 2 (5 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OpenClawEngine._extract_responses_output_text (cognitive 29) src/flock/integrations/openclaw/engine.py:1196— OpenClawEngine._extract_responses_output_text has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (23 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TournamentBracket.TournamentBracket (cognitive 28) src/flock/frontend/src/components/graph/TournamentBracket.tsx:95— TournamentBracket.TournamentBracket has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 15 (17 pts), if/else 6, boolean chains 5 (nesting depth added 2). Most of this is not in the body itself: 1 of the 28 points is its own statement and the rest belongs to 10 function items inside it that branch (a function literal at line 284, lineColor, 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.
GraphCanvas.GraphCanvas (cognitive 28) src/flock/frontend/src/components/graph/GraphCanvas.tsx:44— GraphCanvas.GraphCanvas has cognitive complexity 28 (threshold 15). Drivers by points: if/else 14, boolean chains 11, ternaries 1 (2 pts), match/switch 1 (nesting depth added 1). Most of this is not in the body itself: 6 of the 28 points are its own statements and the rest belongs to 11 function literals inside it that branch (lines 196, 291, 178, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
RunStatusTab.RunStatusTab (cognitive 28) src/flock/frontend/src/components/details/RunStatusTab.tsx:22— RunStatusTab.RunStatusTab has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 7 (15 pts), boolean chains 5, if/else 5, match/switch 2, error handling 1 (nesting depth added 8). Most of this is not in the body itself: 6 of the 28 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 244, a function literal at line 29, a function literal at line 48, …). 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.
WebSocketClient.updateFilterStateFromPublishedMessage (cognitive 27) src/flock/frontend/src/services/websocket.ts:63— WebSocketClient.updateFilterStateFromPublishedMessage has cognitive complexity 27 (threshold 15). Drivers by points: ternaries 11 (13 pts), boolean chains 10, if/else 4 (nesting depth added 2). Of this number, 25 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
GraphAssembler._build_logic_config_for_subscription (cognitive 26) src/flock/api/graph_builder.py:1256— GraphAssembler._build_logic_config_for_subscription has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (14 pts), ternaries 5 (10 pts), boolean chains 2 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
helpers._build_logic_config (cognitive 26) src/flock/components/server/control/helpers.py:245— helpers._build_logic_config has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (14 pts), ternaries 5 (10 pts), boolean chains 2 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
dapr_state_blackboard_store._build_dapr_query (cognitive 26) src/flock/storage/dapr/dapr_state_blackboard_store.py:106— dapr_state_blackboard_store._build_dapr_query has cognitive complexity 26 (threshold 15). Drivers by points: if/else 14 (26 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WebSocketClient.setupEventHandlers (cognitive 26) src/flock/frontend/src/services/websocket.ts:166— WebSocketClient.setupEventHandlers has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (12 pts), boolean chains 10, ternaries 3 (4 pts) (nesting depth added 2). None of this is in the body itself: all 26 points belong to 7 function literals inside it that branch (lines 219, 182, 261, …). 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.
TracingSettings.TracingSettings (cognitive 26) src/flock/frontend/src/components/settings/TracingSettings.tsx:30— TracingSettings.TracingSettings has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 7 (9 pts), if/else 8, boolean chains 5, error handling 4 (nesting depth added 2). Most of this is not in the body itself: 8 of the 26 points are its own statements and the rest belongs to 7 function items inside it that branch (handleClearTraces, handleSaveSettings, loadTraceServices, …). 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.
trace_and_logged._serialize_value (cognitive 25) src/flock/logging/trace_and_logged.py:100— trace_and_logged._serialize_value has cognitive complexity 25 (threshold 15). Drivers by points: if/else 12 (16 pts), error handling 3 (6 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Context.fire_time (cognitive 25) src/flock/utils/runtime.py:364— Context.fire_time has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (18 pts), error handling 1 (4 pts), boolean chains 2, ternaries 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Flock.run_until (cognitive 24) src/flock/core/orchestrator.py:789— Flock.run_until has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (23 pts), loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_QuestionMeta.__new__ (cognitive 24) src/flock/decisions/choice.py:144— _QuestionMeta.__new__ has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 3, loops 3, ternaries 3 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OpenClawEngine._materialize_artifacts_for_output_group (cognitive 24) src/flock/integrations/openclaw/engine.py:966— OpenClawEngine._materialize_artifacts_for_output_group has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (17 pts), loops 3 (7 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Flock.get_correlation_status (cognitive 23) src/flock/core/orchestrator.py:362— Flock.get_correlation_status has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 3 (6 pts), boolean chains 3 (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.
DSPySignatureBuilder.prepare_execution_payload_for_output_group (cognitive 23) src/flock/engines/dspy/signature_builder.py:364— DSPySignatureBuilder.prepare_execution_payload_for_output_group has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 2 (4 pts), ternaries 1 (4 pts), boolean chains 2 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FlockMCPClient.__init__ (cognitive 23) src/flock/mcp/client.py:231— FlockMCPClient.__init__ has cognitive complexity 23 (threshold 15). Drivers by points: if/else 17 (21 pts), boolean chains 2 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
WebSocketClient.handleMessage (cognitive 23) src/flock/frontend/src/services/websocket.ts:511— WebSocketClient.handleMessage has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 5, error handling 2 (4 pts), ternaries 1 (nesting depth added 4). Of this number, 20 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
LiveOutputTab.LiveOutputTab (cognitive 23) src/flock/frontend/src/components/details/LiveOutputTab.tsx:13— LiveOutputTab.LiveOutputTab has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 4, ternaries 3 (4 pts), error handling 1, loops 1 (nesting depth added 5). Most of this is not in the body itself: 5 of the 23 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 68, 24, 87, …). 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.
MultiSelect.MultiSelect (cognitive 22) src/flock/frontend/src/components/settings/MultiSelect.tsx:21— MultiSelect.MultiSelect has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 7, ternaries 5, match/switch 1 (nesting depth added 4). Most of this is not in the body itself: 6 of the 22 points are its own statements and the rest belongs to 7 function items inside it that branch (handleKeyDown, a function literal at line 43, a function literal at line 36, …). 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.
SavedFiltersControl.SavedFiltersControl (cognitive 22) src/flock/frontend/src/components/filters/SavedFiltersControl.tsx:6— SavedFiltersControl.SavedFiltersControl has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (13 pts), boolean chains 5, error handling 3, ternaries 1 (nesting depth added 1). Most of this is not in the body itself: 4 of the 22 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 31, handleSavePreset, handleApplyPreset, …). 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.
SemanticContextProvider.get_context (cognitive 21) src/flock/semantic/context_provider.py:81— SemanticContextProvider.get_context has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (14 pts), error handling 4 (5 pts), boolean chains 1, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DashboardLayout.DashboardLayout (cognitive 21) src/flock/frontend/src/components/layout/DashboardLayout.tsx:21— DashboardLayout.DashboardLayout has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 13, if/else 4 (5 pts), boolean chains 3 (nesting depth added 1). Of this number, 16 points are the body's own statements and 5 belong to 3 function items inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
MCPIntegration.configure_servers (cognitive 20) src/flock/agent/mcp_integration.py:109— MCPIntegration.configure_servers has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 2, loops 1 (2 pts), ternaries 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GraphAssembler._derive_blackboard_edges (cognitive 20) src/flock/api/graph_builder.py:1059— GraphAssembler._derive_blackboard_edges has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 4 (7 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
helpers._compute_agent_status (cognitive 20) src/flock/components/server/control/helpers.py:211— helpers._compute_agent_status has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (18 pts), boolean chains 1, loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
themed_formatter.create_rich_renderable (cognitive 20) src/flock/logging/formatters/themed_formatter.py:238— themed_formatter.create_rich_renderable has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (9 pts), loops 2 (5 pts), ternaries 2 (4 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
VersionBumper.bump_versions (cognitive 19) scripts/bump_version.py:201— VersionBumper.bump_versions has cognitive complexity 19 (threshold 15). Drivers by points: if/else 15 (16 pts), boolean chains 2, ternaries 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
GraphAssembler._apply_pending_label_offsets (cognitive 19) src/flock/api/graph_builder.py:880— GraphAssembler._apply_pending_label_offsets has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 5 (8 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.
DaprStateBlackboardStore._query_via_dapr_api (cognitive 19) src/flock/storage/dapr/dapr_state_blackboard_store.py:469— DaprStateBlackboardStore._query_via_dapr_api has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (12 pts), error handling 1 (3 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
helpers._get_correlation_groups (cognitive 18) src/flock/components/server/control/helpers.py:16— helpers._get_correlation_groups has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (13 pts), ternaries 2 (4 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DecisionEngine._wire_questions (cognitive 18) src/flock/decisions/engine.py:829— DecisionEngine._wire_questions has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 3 (8 pts), if/else 2 (5 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
graph.decision_view (cognitive 18) src/flock/decisions/graph.py:174— graph.decision_view has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11, boolean chains 7. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
theme_builder.create_rich_renderable (cognitive 18) src/flock/logging/formatters/theme_builder.py:227— theme_builder.create_rich_renderable has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (8 pts), loops 2 (5 pts), ternaries 2 (4 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FlockStreamableHttpClient.create_transport (cognitive 18) src/flock/mcp/servers/streamable_http/flock_streamable_http_server.py:67— FlockStreamableHttpClient.create_transport has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (17 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LoggingUtility._consume_stream (cognitive 18) src/flock/utils/utilities.py:263— LoggingUtility._consume_stream has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 4, ternaries 1 (3 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
check_version_bump.main (cognitive 17) scripts/check_version_bump.py:103— check_version_bump.main has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GraphAssembler._derive_agent_edges (cognitive 17) src/flock/api/graph_builder.py:764— GraphAssembler._derive_agent_edges has cognitive complexity 17 (threshold 15). Drivers by points: if/else 3 (8 pts), loops 3 (4 pts), boolean chains 3, ternaries 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GuardComponent._extract_context_documents (cognitive 17) src/flock/components/agent/guard.py:185— GuardComponent._extract_context_documents has cognitive complexity 17 (threshold 15). Drivers by points: if/else 3 (10 pts), loops 3 (7 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TimerComponent._wait_for_next_fire (cognitive 17) src/flock/components/orchestrator/scheduling/timer.py:316— TimerComponent._wait_for_next_fire has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (14 pts), ternaries 1 (3 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_HttpDecisionProvider.decide_many (cognitive 17) src/flock/decisions/providers.py:426— _HttpDecisionProvider.decide_many has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (7 pts), boolean chains 3, error handling 2 (3 pts), ternaries 2 (3 pts), loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DSPyArtifactMaterializer.select_output_payload (cognitive 17) src/flock/engines/dspy/artifact_materializer.py:223— DSPyArtifactMaterializer.select_output_payload has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (12 pts), ternaries 1 (4 pts), loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FoundryResponsesAdapter._handle (cognitive 17) src/flock/integrations/foundry/adapter.py:217— FoundryResponsesAdapter._handle has cognitive complexity 17 (threshold 15). Drivers by points: error handling 6, ternaries 2 (4 pts), if/else 3, loops 2 (3 pts), boolean chains 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OpenClawEngine._extract_error_message (cognitive 17) src/flock/integrations/openclaw/engine.py:1299— OpenClawEngine._extract_error_message has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 2 (5 pts), boolean chains 1, error handling 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OpenClawSSEDispatcher._extract_completed_text (cognitive 17) src/flock/integrations/openclaw/streaming.py:246— OpenClawSSEDispatcher._extract_completed_text has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 2 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ArtifactManager.publish (cognitive 17) src/flock/orchestrator/artifact_manager.py:107— ArtifactManager.publish has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 5 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DaprStateBlackboardStore._query_via_index_scan (cognitive 17) src/flock/storage/dapr/dapr_state_blackboard_store.py:518— DaprStateBlackboardStore._query_via_index_scan has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (8 pts), loops 3 (5 pts), boolean chains 2, error handling 1 (2 pts) (nesting depth added 4). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
cli_helper.kingfisher (cognitive 17) src/flock/utils/cli_helper.py:143— cli_helper.kingfisher has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (7 pts), ternaries 1 (4 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GraphAssembler._build_pending_join_edges (cognitive 16) src/flock/api/graph_builder.py:919— GraphAssembler._build_pending_join_edges has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 3 (6 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_Workflow._loop (cognitive 16) src/flock/application/application.py:326— _Workflow._loop has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (13 pts), boolean chains 2, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TimerComponent._calculate_next_fire_time (cognitive 16) src/flock/components/orchestrator/scheduling/timer.py:271— TimerComponent._calculate_next_fire_time has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (9 pts), ternaries 3 (7 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ArtifactsComponent._publish_upload (cognitive 16) src/flock/components/server/artifacts/artifacts_component.py:307— ArtifactsComponent._publish_upload has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (6 pts), boolean chains 5, error handling 4, loops 1 (nesting depth added 1). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Flock._run_initialize (cognitive 16) src/flock/core/orchestrator.py:1283— Flock._run_initialize has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (10 pts), boolean chains 4, loops 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Subscription._matches_text_predicates (cognitive 16) src/flock/core/subscription.py:324— Subscription._matches_text_predicates has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (9 pts), error handling 3 (4 pts), boolean chains 2, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DecisionEngine._run_tournament (cognitive 16) src/flock/decisions/engine.py:746— DecisionEngine._run_tournament has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 2 (3 pts), boolean chains 2, ternaries 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OpenClawSSEConsumer._iter_frames (cognitive 16) src/flock/integrations/openclaw/streaming.py:431— OpenClawSSEConsumer._iter_frames has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), error handling 1 (3 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (streaming.parse_sse_lines) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
streaming.parse_sse_lines (cognitive 16) src/flock/integrations/openclaw/streaming.py:49— streaming.parse_sse_lines has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), error handling 1 (3 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (OpenClawSSEConsumer._iter_frames) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
auto_trace._parse_trace_filters (cognitive 16) src/flock/logging/auto_trace.py:123— auto_trace._parse_trace_filters has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), error handling 2 (4 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FlockMCPConfiguration.from_dict (cognitive 16) src/flock/mcp/config.py:371— FlockMCPConfiguration.from_dict has cognitive complexity 16 (threshold 15). Drivers by points: error handling 4 (8 pts), if/else 8 (nesting depth added 4). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
FlockSSEClient.create_transport (cognitive 16) src/flock/mcp/servers/sse/flock_sse_server.py:60— FlockSSEClient.create_transport has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
visibility_utils._validate_visibility (cognitive 16) src/flock/utils/visibility_utils.py:141— visibility_utils._validate_visibility has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 4 (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.
NodeDetailWindow.NodeDetailWindow (cognitive 16) src/flock/frontend/src/components/details/NodeDetailWindow.tsx:13— NodeDetailWindow.NodeDetailWindow has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 9 (10 pts), boolean chains 3, if/else 3 (nesting depth added 1). Most of this is not in the body itself: 7 of the 16 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 154, 176, 182). 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.
ThemeSelector.ThemeSelector (cognitive 16) src/flock/frontend/src/components/settings/ThemeSelector.tsx:14— ThemeSelector.ThemeSelector has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 10, error handling 3, if/else 2, ternaries 1. Of this number, 10 points are the body's own statements and 6 belong to 6 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D22 · Internal API Consistency· Redundant naming for synchronous/asynchronous execution. The distinction between `run` and `run_async` is implicit in the name but explicit in the signature only by convention (or lack of return type). It is more consistent to use `start`/`start_async` or `serve`/`serve_async` to clearly indicate lifecycle management rather than execution style, or to have a single `start` method that handles both via a parameter. · ×1
Redundant naming for synchronous/asynchronous execution. The distinction between `run` and `run_async` is implicit in the name but explicit in the signature only by convention (or lack of return type). It is more consistent to use `start`/`start_async` or `serve`/`serve_async` to clearly indicate lifecycle management rather than execution style, or to have a single `start` method that handles both via a parameter. — Unify to `start()` and `start_async()` or `serve()` and `serve_async()` across all HTTP service implementations to align with standard web server lifecycle patterns. (signatures: BaseHTTPService.run(self, host: str, port: int): None | BaseHTTPService.run_async(self, host: str, port: int): None | BlackboardHTTPService.run(self, host: str, port: int): None | BlackboardHTTPService.run_async(self, host: str, port: int): None)
D22 · Internal API Consistency· Ambiguous intent of 'execute'. In `RunHandle`, `execute` likely triggers the actual agent run. In `Pipeline`, `execute` likely triggers the entire chain. While technically distinct scopes, the method name is identical. If `RunHandle` is a component of a `Pipeline`, the naming is consistent. However, `RunHandle` also has `then`, suggesting a builder pattern, while `Pipeline` also has `then`. The duplication of `then` and `execute` on both types suggests they might be interchangeable or one is a wrapper for the other, creating confusion about whether to use the Handle or the Pipeline for execution. · ×1
Ambiguous intent of 'execute'. In `RunHandle`, `execute` likely triggers the actual agent run. In `Pipeline`, `execute` likely triggers the entire chain. While technically distinct scopes, the method name is identical. If `RunHandle` is a component of a `Pipeline`, the naming is consistent. However, `RunHandle` also has `then`, suggesting a builder pattern, while `Pipeline` also has `then`. The duplication of `then` and `execute` on both types suggests they might be interchangeable or one is a wrapper for the other, creating confusion about whether to use the Handle or the Pipeline for execution. — Clarify if `RunHandle` is a terminal execution object or a builder step. If it's a builder step, it should not have `execute`. If it's a terminal object, `Pipeline` should not expose `execute` if it's meant to be built and then executed via a different entry point. Consider renaming `RunHandle.execute` to `RunHandle.run` to distinguish single-agent execution from pipeline execution. (signatures: RunHandle.execute(self): list[Artifact] | Pipeline.execute(self): list[Artifact])
D22 · Internal API Consistency· Duplicate lifecycle hook interfaces. `ComponentLifecycle` and `AgentComponent` expose nearly identical lifecycle methods (`run_*` vs `on_*`) with the same signatures and intent (pre/post consume, evaluate, publish, error, terminate). This creates two parallel ways to hook into the agent lifecycle, confusing users about which interface to implement. · ×1
Duplicate lifecycle hook interfaces. `ComponentLifecycle` and `AgentComponent` expose nearly identical lifecycle methods (`run_*` vs `on_*`) with the same signatures and intent (pre/post consume, evaluate, publish, error, terminate). This creates two parallel ways to hook into the agent lifecycle, confusing users about which interface to implement. — Remove one of the interfaces. `AgentComponent` appears to be the more modern/standard naming convention (`on_*`). Deprecate `ComponentLifecycle` or ensure it is an internal implementation detail not exposed in the public API surface. (signatures: ComponentLifecycle.run_pre_consume(...) | ComponentLifecycle.run_pre_evaluate(...) | ComponentLifecycle.run_post_evaluate(...) | ComponentLifecycle.run_post_publish(...) | ComponentLifecycle.run_error(...) | ComponentLifecycle.run_terminate(...) | AgentComponent.on_pre_consume(...) | AgentComponent.on_pre_evaluate(...) | AgentComponent.on_post_evaluate(...) | AgentComponent.on_post_publish(...) | AgentComponent.on_error(...) | AgentComponent.on_terminate(...))
MethodTooLong: WebSocketClient.setupEventHandlers src/flock/frontend/src/services/websocket.ts:166— MethodTooLong — setupEventHandlers runs 109 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 9 over it, 1.09× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Near-duplicate member pair (26 shared lines) src/flock/logging/formatters/theme_builder.py:233— src/flock/logging/formatters/theme_builder.py:233-297 | src/flock/logging/formatters/themed_formatter.py:245-331 — These two members are variants of one another: 26 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.
Duplicated block (99–103 lines × 2) src/flock/logging/formatters/theme_builder.py:90— src/flock/logging/formatters/theme_builder.py:90-188 | src/flock/logging/formatters/themed_formatter.py:83-185 — before extracting anything, compare `src/flock/logging/formatters/theme_builder.py` and `src/flock/logging/formatters/themed_formatter.py` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 213 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/flock/logging/formatters/theme_builder.py:90` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (46–48 lines × 2) src/flock/core/agent.py:1385— src/flock/core/agent.py:1385-1432 | src/flock/core/agent.py:1523-1568 — 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 (27–47 lines × 2) src/flock/api/graph_builder.py:1257— src/flock/api/graph_builder.py:1257-1283 | src/flock/components/server/control/helpers.py:251-297 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (23–38 lines × 2) src/flock/core/orchestrator.py:731— src/flock/core/orchestrator.py:731-768 | src/flock/core/orchestrator.py:850-872 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (37 lines × 2) src/flock/mcp/types/types.py:206— src/flock/mcp/types/types.py:206-242 | src/flock/mcp/types/types.py:293-329 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (32–36 lines × 2) src/flock/integrations/openclaw/streaming.py:81— src/flock/integrations/openclaw/streaming.py:81-116 | src/flock/integrations/openclaw/streaming.py:458-489 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (30 lines × 2) src/flock/logging/trace_and_logged.py:306— src/flock/logging/trace_and_logged.py:306-335 | src/flock/logging/trace_and_logged.py:358-387 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (25–27 lines × 2) src/flock/api/graph_builder.py:1290— src/flock/api/graph_builder.py:1290-1316 | src/flock/components/server/control/helpers.py:302-326 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/flock/api/graph_builder.py:1290` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (19–26 lines × 2) src/flock/logging/formatters/theme_builder.py:206— src/flock/logging/formatters/theme_builder.py:206-224 | src/flock/logging/formatters/themed_formatter.py:210-235 — before extracting anything, compare `src/flock/logging/formatters/theme_builder.py` and `src/flock/logging/formatters/themed_formatter.py` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 213 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. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (19–25 lines × 2) src/flock/orchestrator/batch_accumulator.py:120— src/flock/orchestrator/batch_accumulator.py:120-138 | src/flock/orchestrator/batch_accumulator.py:152-176 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (23–24 lines × 2) src/flock/agent/component_lifecycle.py:133— src/flock/agent/component_lifecycle.py:133-155 | src/flock/agent/component_lifecycle.py:173-196 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (22–24 lines × 2) src/flock/integrations/openclaw/engine.py:164— src/flock/integrations/openclaw/engine.py:164-187 | src/flock/integrations/openclaw/engine.py:215-236 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/flock/integrations/openclaw/engine.py:164` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (24 lines × 2) src/flock/integrations/openclaw/streaming.py:55— src/flock/integrations/openclaw/streaming.py:55-78 | src/flock/integrations/openclaw/streaming.py:432-455 — 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–19 lines × 2) src/flock/api/service.py:440— src/flock/api/service.py:440-456 | src/flock/components/server/agents/agents_component.py:136-154 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/flock/components/server/agents/agents_component.py:136` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (17 lines × 2) src/flock/engines/dspy/streaming_executor.py:422— src/flock/engines/dspy/streaming_executor.py:422-438 | src/flock/integrations/openclaw/engine.py:561-577 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (15 lines × 2) src/flock/mcp/servers/sse/flock_sse_server.py:83— src/flock/mcp/servers/sse/flock_sse_server.py:83-97 | src/flock/mcp/servers/streamable_http/flock_streamable_http_server.py:97-111 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (14 lines × 2) src/flock/logging/formatters/theme_builder.py:26— src/flock/logging/formatters/theme_builder.py:26-39 | src/flock/logging/formatters/themed_formatter.py:26-43 — before extracting anything, compare `src/flock/logging/formatters/theme_builder.py` and `src/flock/logging/formatters/themed_formatter.py` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 213 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 × 3) src/flock/components/server/traces/trace_component.py:434— src/flock/components/server/traces/trace_component.py:434-442 | src/flock/components/server/traces/trace_component.py:542-550 | src/flock/components/server/traces/trace_component.py:592-600 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/flock/components/server/traces/trace_component.py:434` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (4–8 lines × 4) src/flock/components/server/agents/agents_component.py:160— src/flock/components/server/agents/agents_component.py:160-163 | src/flock/components/server/artifacts/artifacts_component.py:444-451 | src/flock/components/server/artifacts/artifacts_component.py:558-565 | src/flock/components/server/artifacts/artifacts_component.py:640-647 — there are 4 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 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/flock/components/server/artifacts/artifacts_component.py:444` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7–8 lines × 2) src/flock/logging/trace_and_logged.py:287— src/flock/logging/trace_and_logged.py:287-293 | src/flock/logging/trace_and_logged.py:338-345 — 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 (4–7 lines × 4) src/flock/api/service.py:325— src/flock/api/service.py:325-331 | src/flock/api/service.py:370-376 | src/flock/api/service.py:461-464 | src/flock/components/server/agents/agents_component.py:163-166 — there are 4 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 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/flock/api/service.py:325` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/flock/components/server/agents/agents_component.py:161` calls `Query` and `src/flock/api/service.py:461` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5–7 lines × 2) src/flock/logging/formatters/theme_builder.py:272— src/flock/logging/formatters/theme_builder.py:272-276 | src/flock/logging/formatters/themed_formatter.py:288-294 — before extracting anything, compare `src/flock/logging/formatters/theme_builder.py` and `src/flock/logging/formatters/themed_formatter.py` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 213 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/flock/logging/formatters/theme_builder.py:272` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (6 lines × 3) src/flock/logging/formatters/theme_builder.py:243— src/flock/logging/formatters/theme_builder.py:243-248 | src/flock/logging/formatters/themed_formatter.py:258-264 | src/flock/logging/formatters/themed_formatter.py:422-429 — before extracting anything, compare `src/flock/logging/formatters/theme_builder.py` and `src/flock/logging/formatters/themed_formatter.py` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 213 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/flock/logging/formatters/theme_builder.py:243` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 3) src/flock/logging/formatters/theme_builder.py:272— src/flock/logging/formatters/theme_builder.py:272-276 | src/flock/logging/formatters/themed_formatter.py:288-292 | src/flock/logging/formatters/themed_formatter.py:453-459 — before extracting anything, compare `src/flock/logging/formatters/theme_builder.py` and `src/flock/logging/formatters/themed_formatter.py` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 213 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/flock/logging/formatters/theme_builder.py:272` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) src/flock/logging/formatters/theme_builder.py:281— src/flock/logging/formatters/theme_builder.py:281-285 | src/flock/logging/formatters/themed_formatter.py:301-306 — before extracting anything, compare `src/flock/logging/formatters/theme_builder.py` and `src/flock/logging/formatters/themed_formatter.py` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 213 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/flock/logging/formatters/theme_builder.py:281` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (7 lines × 3) src/flock/integrations/foundry/__init__.py:73— src/flock/integrations/foundry/__init__.py:73-79 | src/flock/storage/__init__.py:87-93 | src/flock/storage/dapr/__init__.py:79-85 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (54–55 lines × 3) examples/12-dapr/inmemory/flock_dapr_inmemory.py:76— examples/12-dapr/inmemory/flock_dapr_inmemory.py:76-130 | examples/12-dapr/postgresql_unencrypted/flock_dapr_postgresql.py:77-130 | examples/12-dapr/redis_encrypted/flock_dapr_redis.py:77-130 — `examples/12-dapr/inmemory/flock_dapr_inmemory.py` and `examples/12-dapr/postgresql_unencrypted/flock_dapr_postgresql.py` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 2 separate duplicated blocks between them, totalling at least 85 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `examples/12-dapr/inmemory/flock_dapr_inmemory.py:76` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (28–43 lines × 3) examples/09-server-components/05_websocket_component.py:82— examples/09-server-components/05_websocket_component.py:82-124 | examples/09-server-components/06_artifacts_component.py:86-114 | examples/09-server-components/11_tracing_component.py:113-140 — before extracting anything, compare `examples/09-server-components/05_websocket_component.py` and `examples/09-server-components/06_artifacts_component.py` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 133 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 (22–40 lines × 2) examples/09-server-components/08_control_routes_component.py:105— examples/09-server-components/08_control_routes_component.py:105-144 | examples/09-server-components/12_complete_composition.py:246-267 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `examples/09-server-components/08_control_routes_component.py:105` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (21–36 lines × 4) examples/09-server-components/06_artifacts_component.py:122— examples/09-server-components/06_artifacts_component.py:122-142 | examples/09-server-components/08_control_routes_component.py:97-121 | examples/09-server-components/10_themes_component.py:98-133 | examples/09-server-components/11_tracing_component.py:148-181 — before extracting anything, compare `examples/09-server-components/06_artifacts_component.py` and `examples/09-server-components/08_control_routes_component.py` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 141 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `examples/09-server-components/08_control_routes_component.py:97` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (20–33 lines × 5) examples/09-server-components/06_artifacts_component.py:127— examples/09-server-components/06_artifacts_component.py:127-146 | examples/09-server-components/08_control_routes_component.py:104-124 | examples/09-server-components/10_themes_component.py:105-137 | examples/09-server-components/11_tracing_component.py:153-185 | examples/09-server-components/12_complete_composition.py:245-264 — before extracting anything, compare `examples/09-server-components/06_artifacts_component.py` and `examples/09-server-components/08_control_routes_component.py` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 141 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `examples/09-server-components/08_control_routes_component.py:104` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (30 lines × 3) examples/12-dapr/inmemory/flock_dapr_inmemory.py:138— examples/12-dapr/inmemory/flock_dapr_inmemory.py:138-167 | examples/12-dapr/postgresql_unencrypted/flock_dapr_postgresql.py:139-168 | examples/12-dapr/redis_encrypted/flock_dapr_redis.py:139-168 — `examples/12-dapr/inmemory/flock_dapr_inmemory.py` and `examples/12-dapr/postgresql_unencrypted/flock_dapr_postgresql.py` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 2 separate duplicated blocks between them, totalling at least 85 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `examples/12-dapr/inmemory/flock_dapr_inmemory.py:138` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (23 lines × 3) examples/09-server-components/04_health_component.py:100— examples/09-server-components/04_health_component.py:100-122 | examples/09-server-components/06_artifacts_component.py:77-99 | examples/09-server-components/11_tracing_component.py:104-126 — before extracting anything, compare `examples/09-server-components/06_artifacts_component.py` and `examples/09-server-components/11_tracing_component.py` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 207 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (20 lines × 6) examples/09-server-components/05_websocket_component.py:81— examples/09-server-components/05_websocket_component.py:81-100 | examples/09-server-components/06_artifacts_component.py:85-104 | examples/09-server-components/07_agents_component.py:138-157 | examples/09-server-components/08_control_routes_component.py:86-105 | examples/09-server-components/10_themes_component.py:87-106 | examples/09-server-components/11_tracing_component.py:112-131 — before extracting anything, compare `examples/09-server-components/05_websocket_component.py` and `examples/09-server-components/06_artifacts_component.py` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 133 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 (19–20 lines × 2) examples/09-server-components/01_authentication_component.py:28— examples/09-server-components/01_authentication_component.py:28-47 | examples/09-server-components/01_authentication_component.py:187-205 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `examples/09-server-components/01_authentication_component.py:28` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12–19 lines × 2) examples/09-server-components/01_authentication_component.py:141— examples/09-server-components/01_authentication_component.py:141-159 | examples/09-server-components/01_authentication_component.py:301-312 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `examples/09-server-components/01_authentication_component.py:141` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 2) examples/09-server-components/04_health_component.py:108— examples/09-server-components/04_health_component.py:108-126 | examples/09-server-components/09_static_files_component.py:225-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 (18 lines × 8) examples/09-server-components/04_health_component.py:107— examples/09-server-components/04_health_component.py:107-125 | examples/09-server-components/05_websocket_component.py:80-99 | examples/09-server-components/06_artifacts_component.py:84-103 | examples/09-server-components/07_agents_component.py:137-156 | examples/09-server-components/08_control_routes_component.py:85-104 | examples/09-server-components/09_static_files_component.py:224-241 | examples/09-server-components/10_themes_component.py:86-105 | examples/09-server-components/11_tracing_component.py:111-130 — before extracting anything, compare `examples/09-server-components/05_websocket_component.py` and `examples/09-server-components/06_artifacts_component.py` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 133 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) examples/03-hackathon/07_joinspec_correlation.py:150— examples/03-hackathon/07_joinspec_correlation.py:150-166 | examples/03-hackathon/07_joinspec_correlation.py:187-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. Read the line range as the matched WINDOW rather than a finished unit: at `examples/03-hackathon/07_joinspec_correlation.py:187` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11–18 lines × 2) examples/09-server-components/01_authentication_component.py:137— examples/09-server-components/01_authentication_component.py:137-154 | examples/09-server-components/01_authentication_component.py:288-298 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (18 lines × 2) examples/09-server-components/05_websocket_component.py:62— examples/09-server-components/05_websocket_component.py:62-79 | examples/09-server-components/06_artifacts_component.py:71-88 — before extracting anything, compare `examples/09-server-components/05_websocket_component.py` and `examples/09-server-components/06_artifacts_component.py` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 133 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `examples/09-server-components/05_websocket_component.py:62` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 5) examples/09-server-components/05_websocket_component.py:68— examples/09-server-components/05_websocket_component.py:68-84 | examples/09-server-components/06_artifacts_component.py:124-142 | examples/09-server-components/08_control_routes_component.py:101-121 | examples/09-server-components/10_themes_component.py:102-133 | examples/09-server-components/11_tracing_component.py:150-181 — before extracting anything, compare `examples/09-server-components/05_websocket_component.py` and `examples/09-server-components/06_artifacts_component.py` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 133 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `examples/09-server-components/08_control_routes_component.py:101` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (14–16 lines × 3) examples/15-decisions/07_escalation.py:136— examples/15-decisions/07_escalation.py:136-151 | examples/15-decisions/08_voting.py:134-147 | examples/15-decisions/09_shadow.py:126-139 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `examples/15-decisions/07_escalation.py:136` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14–15 lines × 2) examples/02-patterns/visibility/01_basic_visibility.py:75— examples/02-patterns/visibility/01_basic_visibility.py:75-88 | examples/02-patterns/visibility/01_basic_visibility.py:91-105 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `examples/02-patterns/visibility/01_basic_visibility.py:89` calls `run_until_idle` and `examples/02-patterns/visibility/01_basic_visibility.py:72` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12–13 lines × 2) examples/05-engines/potion_batch_engine.py:142— examples/05-engines/potion_batch_engine.py:142-153 | examples/06-agent-components/cheer_meter_component.py:102-114 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `examples/05-engines/potion_batch_engine.py:142` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 3) examples/03-hackathon/09_mcp_web_researcher.py:258— examples/03-hackathon/09_mcp_web_researcher.py:258-265 | examples/03-hackathon/10_mcp_filesystem_roots.py:219-226 | examples/03-hackathon/11_agent_components_news_batching.py:360-369 — 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.
Low cohesion: Flock (LCOM4 5) src/flock/core/orchestrator.py:74— Flock's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Duplication concentrated across 8 sibling directories (11 clone groups) src/flock/frontend/src/components/common/ImageThumbnails.tsx:25— 11 duplicated blocks under src/flock/frontend/src/components/ have copies in at least two of the sibling directories common, controls, details, filters, graph, layout (+2 more sibling(s) not listed) — 6 of them are reported below, and 5 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 11 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 11 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 11 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Wholesale file copy (62 identical lines × 2 files) src/flock/frontend/src/components/graph/PendingBatchEdge.tsx:1— src/flock/frontend/src/components/graph/PendingBatchEdge.tsx:1 · src/flock/frontend/src/components/graph/PendingJoinEdge.tsx:1 — these 2 files are line-for-line copies of one another — 62 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Duplicated block (60 lines × 2 locations) src/flock/frontend/src/components/details/MessageDetailWindow.tsx:62— src/flock/frontend/src/components/details/MessageDetailWindow.tsx:62 · src/flock/frontend/src/components/details/NodeDetailWindow.tsx:31 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (50 matched lines × 2 locations) · ×1
Duplicated block with local edits (50 matched lines × 2 locations) src/flock/frontend/src/components/settings/AppearanceSettings.tsx:122— src/flock/frontend/src/components/settings/AppearanceSettings.tsx:122 · src/flock/frontend/src/components/settings/GraphSettings.tsx:27 — the two spans are one implementation copied and then locally edited — 282 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 (49 matched lines × 2 locations) · ×1
Duplicated block with local edits (49 matched lines × 2 locations) src/flock/frontend/src/components/graph/MessageFlowEdge.tsx:31— src/flock/frontend/src/components/graph/MessageFlowEdge.tsx:31 · src/flock/frontend/src/components/graph/TransformEdge.tsx:27 — the two spans are one implementation copied and then locally edited — 278 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (47 lines × 2 locations) src/flock/frontend/src/components/details/MessageHistoryTab.tsx:156— src/flock/frontend/src/components/details/MessageHistoryTab.tsx:156 · src/flock/frontend/src/components/details/RunStatusTab.tsx:113 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (44 lines × 2 locations) src/flock/frontend/src/components/graph/GraphCanvas.tsx:476— src/flock/frontend/src/components/graph/GraphCanvas.tsx:476 · src/flock/frontend/src/components/graph/GraphCanvas.tsx:700 — 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 (38 lines × 2 locations) src/flock/frontend/src/store/graphStore.ts:135— src/flock/frontend/src/store/graphStore.ts:135 · src/flock/frontend/src/store/graphStore.ts:191 — 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 (36 lines × 2 locations) src/flock/frontend/src/components/details/MessageDetailWindow.tsx:158— src/flock/frontend/src/components/details/MessageDetailWindow.tsx:158 · src/flock/frontend/src/components/details/NodeDetailWindow.tsx:117 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication· Duplicated block with local edits (35 matched lines × 2 locations) · ×1
Duplicated block with local edits (35 matched lines × 2 locations) src/flock/frontend/src/store/moduleStore.ts:29— src/flock/frontend/src/store/moduleStore.ts:29 · src/flock/frontend/src/store/uiStore.ts:89 — the two spans are one implementation copied and then locally edited — 196 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (31 lines × 2 locations) src/flock/frontend/src/components/settings/AdvancedSettings.tsx:101— src/flock/frontend/src/components/settings/AdvancedSettings.tsx:101 · src/flock/frontend/src/components/settings/GraphSettings.tsx:55 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R10 · Code Duplication· Duplicated block with local edits (30 matched lines × 2 locations) · ×1
Duplicated block with local edits (30 matched lines × 2 locations) src/flock/frontend/src/components/settings/AdvancedSettings.tsx:14— src/flock/frontend/src/components/settings/AdvancedSettings.tsx:14 · src/flock/frontend/src/components/settings/GraphSettings.tsx:14 — the two spans are one implementation copied and then locally edited — 260 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (22 lines × 5 locations) src/flock/frontend/src/components/graph/GraphCanvas.tsx:523— src/flock/frontend/src/components/graph/GraphCanvas.tsx:523 · src/flock/frontend/src/components/graph/GraphCanvas.tsx:546 · src/flock/frontend/src/components/graph/GraphCanvas.tsx:569 · src/flock/frontend/src/components/graph/GraphCanvas.tsx:592 · +1 more site(s) not listed — all 5 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 (22 lines × 3 locations) src/flock/frontend/src/components/settings/AppearanceSettings.tsx:47— src/flock/frontend/src/components/settings/AppearanceSettings.tsx:47 · src/flock/frontend/src/components/settings/AppearanceSettings.tsx:72 · src/flock/frontend/src/components/settings/AppearanceSettings.tsx:97 — 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 (21 lines × 2 locations) src/flock/frontend/src/store/graphStore.ts:276— src/flock/frontend/src/store/graphStore.ts:276 · src/flock/frontend/src/store/graphStore.ts:308 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (20 lines × 2 locations) src/flock/frontend/src/components/common/ImageThumbnails.tsx:25— src/flock/frontend/src/components/common/ImageThumbnails.tsx:25 · src/flock/frontend/src/components/graph/TournamentBracket.tsx:110 — 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 (18 lines × 2 locations) src/flock/frontend/src/services/api.ts:199— src/flock/frontend/src/services/api.ts:199 · src/flock/frontend/src/services/api.ts:261 — 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) src/flock/frontend/src/components/modules/TraceModuleJaeger.tsx:974— src/flock/frontend/src/components/modules/TraceModuleJaeger.tsx:974 · src/flock/frontend/src/components/modules/TraceModuleJaeger.tsx:1086 — 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 × 5 locations) src/flock/frontend/src/services/indexeddb.ts:439— src/flock/frontend/src/services/indexeddb.ts:439 · src/flock/frontend/src/services/indexeddb.ts:526 · src/flock/frontend/src/services/indexeddb.ts:576 · src/flock/frontend/src/services/indexeddb.ts:626 · +1 more site(s) not listed — 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.
Duplicated block (12 lines × 2 locations) src/flock/frontend/src/components/controls/PublishControl.tsx:549— src/flock/frontend/src/components/controls/PublishControl.tsx:549 · src/flock/frontend/src/components/controls/PublishControl.tsx:580 — 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.
Complex function renderField (cyclomatic 56, cognitive 64) src/flock/frontend/src/components/controls/PublishControl.tsx:320— renderField has cyclomatic complexity 56 and cognitive complexity 64; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 43, cognitive 37) src/flock/frontend/src/components/graph/DecisionDisplay.tsx:1254— (anonymous) has cyclomatic complexity 43 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 37, cognitive 33) src/flock/frontend/src/components/graph/AgentNode.tsx:12— (anonymous) has cyclomatic complexity 37 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function handleKeyDown (cyclomatic 33, cognitive 46) src/flock/frontend/src/hooks/useKeyboardShortcuts.ts:28— handleKeyDown has cyclomatic complexity 33 and cognitive complexity 46; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function updateFilterStateFromPublishedMessage (cyclomatic 33, cognitive 33) src/flock/frontend/src/services/websocket.ts:63— updateFilterStateFromPublishedMessage has cyclomatic complexity 33 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function TraceModuleJaeger (cyclomatic 29, cognitive 28) src/flock/frontend/src/components/modules/TraceModuleJaeger.tsx:73— TraceModuleJaeger has cyclomatic complexity 29 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 27, cognitive 34) src/flock/frontend/src/components/controls/PublishControl.tsx:131— (anonymous) has cyclomatic complexity 27 and cognitive complexity 34; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function resolveNodeOverlaps (cyclomatic 26, cognitive 60) src/flock/frontend/src/services/layout.ts:147— resolveNodeOverlaps has cyclomatic complexity 26 and cognitive complexity 60; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 22, cognitive 32) src/flock/frontend/src/components/controls/PublishControl.tsx:228— (anonymous) has cyclomatic complexity 22 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function HistoricalArtifactsModule (cyclomatic 22, cognitive 18) src/flock/frontend/src/components/modules/HistoricalArtifactsModule.tsx:41— HistoricalArtifactsModule has cyclomatic complexity 22 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 21, cognitive 31) src/flock/frontend/src/components/graph/ScheduledAgentDisplay.tsx:78— (anonymous) has cyclomatic complexity 21 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 21, cognitive 16) src/flock/frontend/src/components/graph/LogicOperationsDisplay.tsx:131— (anonymous) has cyclomatic complexity 21 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function handleMessage (cyclomatic 19, cognitive 20) src/flock/frontend/src/services/websocket.ts:511— handleMessage has cyclomatic complexity 19 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 18, cognitive 15) src/flock/frontend/src/components/graph/ScheduledAgentDisplay.tsx:26— (anonymous) 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.
Complex function DashboardLayout (cyclomatic 17, cognitive 16) src/flock/frontend/src/components/layout/DashboardLayout.tsx:21— DashboardLayout has cyclomatic complexity 17 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 17, cognitive 14) src/flock/frontend/src/components/modules/TraceModuleJaeger.tsx:505— (anonymous) has cyclomatic complexity 17 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function MessageDetailWindow (cyclomatic 16, cognitive 14) src/flock/frontend/src/components/details/MessageDetailWindow.tsx:12— MessageDetailWindow has cyclomatic complexity 16 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 16, cognitive 13) src/flock/frontend/src/components/graph/LogicOperationsDisplay.tsx:323— (anonymous) has cyclomatic complexity 16 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function ThemeSelector (cyclomatic 15, cognitive 13) src/flock/frontend/src/components/settings/ThemeSelector.tsx:14— ThemeSelector has cyclomatic complexity 15 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 15, cognitive 12) src/flock/frontend/src/components/graph/MessageNode.tsx:8— (anonymous) has cyclomatic complexity 15 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files· src/flock/frontend/src/components/modules/TraceModuleJaeger.tsx · ×1
src/flock/frontend/src/components/modules/TraceModuleJaeger.tsx: 1441 lines of code src/flock/frontend/src/components/modules/TraceModuleJaeger.tsx:1— src/flock/frontend/src/components/modules/TraceModuleJaeger.tsx has 1441 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· src/flock/frontend/src/components/graph/DecisionDisplay.tsx · ×1
src/flock/frontend/src/components/graph/DecisionDisplay.tsx: 1317 lines of code src/flock/frontend/src/components/graph/DecisionDisplay.tsx:1— src/flock/frontend/src/components/graph/DecisionDisplay.tsx has 1317 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· src/flock/frontend/src/services/indexeddb.ts · ×1
src/flock/frontend/src/services/indexeddb.ts: 738 lines of code src/flock/frontend/src/services/indexeddb.ts:1— src/flock/frontend/src/services/indexeddb.ts has 738 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· src/flock/frontend/src/components/graph/GraphCanvas.tsx · ×1
src/flock/frontend/src/components/graph/GraphCanvas.tsx: 732 lines of code src/flock/frontend/src/components/graph/GraphCanvas.tsx:1— src/flock/frontend/src/components/graph/GraphCanvas.tsx has 732 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· src/flock/frontend/src/components/controls/PublishControl.tsx · ×1
src/flock/frontend/src/components/controls/PublishControl.tsx: 684 lines of code src/flock/frontend/src/components/controls/PublishControl.tsx:1— src/flock/frontend/src/components/controls/PublishControl.tsx has 684 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/flock/frontend/src/services/websocket.ts · ×1
src/flock/frontend/src/services/websocket.ts: 655 lines of code src/flock/frontend/src/services/websocket.ts:1— src/flock/frontend/src/services/websocket.ts has 655 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· src/flock/frontend/src/services/layout.ts · ×1
src/flock/frontend/src/services/layout.ts: 519 lines of code src/flock/frontend/src/services/layout.ts:1— src/flock/frontend/src/services/layout.ts has 519 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· src/flock/frontend/src/components/graph/LogicOperationsDisplay.tsx · ×1
src/flock/frontend/src/components/graph/LogicOperationsDisplay.tsx: 431 lines of code src/flock/frontend/src/components/graph/LogicOperationsDisplay.tsx:1— src/flock/frontend/src/components/graph/LogicOperationsDisplay.tsx has 431 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· src/flock/frontend/src/store/graphStore.ts · ×1
src/flock/frontend/src/store/graphStore.ts: 426 lines of code src/flock/frontend/src/store/graphStore.ts:1— src/flock/frontend/src/store/graphStore.ts has 426 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· src/flock/frontend/src/components/details/MessageDetailWindow.tsx · ×1
src/flock/frontend/src/components/details/MessageDetailWindow.tsx: 421 lines of code src/flock/frontend/src/components/details/MessageDetailWindow.tsx:1— src/flock/frontend/src/components/details/MessageDetailWindow.tsx has 421 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· src/flock/frontend/src/components/graph/AgentNode.tsx · ×1
src/flock/frontend/src/components/graph/AgentNode.tsx: 415 lines of code src/flock/frontend/src/components/graph/AgentNode.tsx:1— src/flock/frontend/src/components/graph/AgentNode.tsx has 415 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· src/flock/frontend/src/components/modules/HistoricalArtifactsModule.tsx · ×1
src/flock/frontend/src/components/modules/HistoricalArtifactsModule.tsx: 411 lines of code src/flock/frontend/src/components/modules/HistoricalArtifactsModule.tsx:1— src/flock/frontend/src/components/modules/HistoricalArtifactsModule.tsx has 411 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
Dead file (~128 LoC) src/flock/frontend/src/components/common/EmptyState.tsx— no import path from any entry point (3 application, 4 tooling, 34 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~98 LoC) src/flock/frontend/src/utils/mockData.ts— no import path from any entry point (3 application, 4 tooling, 34 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~29 LoC) src/flock/frontend/src/components/common/LoadingSpinner.tsx— no import path from any entry point (3 application, 4 tooling, 34 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~24 LoC) src/flock/frontend/src/utils/artifacts.ts— no import path from any entry point (3 application, 4 tooling, 34 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Unused dependency '@testing-library/user-event' — Declared in src/flock/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.
Unused dependency 'idb' — Declared in src/flock/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.
Unused dependency 'mock-socket' — Declared in src/flock/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.
`async` Promise executor src/flock/frontend/src/services/indexeddb.ts:170— The function passed to `new Promise(…)` is `async`. The constructor ignores what its executor returns, so anything this executor throws — every throw inside an `async` function, including after an `await` — rejects a Promise nobody holds instead of the one being constructed: the outer Promise never settles, whoever awaits it hangs, and the error is reported nowhere. If the body needs `await`, it does not need `new Promise` at all: make the enclosing function `async` and `return` the value (or `throw`) directly. If it wraps a callback API, keep the executor synchronous — call the API and `resolve`/`reject` from its callback — and do the awaiting outside it.
X1 · Async correctness· Task from `loop.create_task` is not kept · ×1
Task from `loop.create_task` is not kept src/flock/patches/dspy_streaming_patch.py:41— The task this creates is not kept anywhere. The event loop holds only a weak reference to its tasks, so a task nobody references can be garbage-collected before it finishes (Python's documentation for `asyncio.create_task`: save a reference to the result); and nothing ever awaits it, so an exception it raises is never handled — it surfaces, if at all, as "Task exception was never retrieved" in a log. Keep the task: `await` it, gather it, start it in an `asyncio.TaskGroup` (`async with asyncio.TaskGroup() as tg: tg.create_task(…)`), or, for genuine fire-and-forget, add it to a set and `task.add_done_callback(tasks.discard)` with a callback that also reads its exception.
README/code drift CONTRIBUTING.md:64— CONTRIBUTING.md installs `#` (`npm install # Install frontend deps`), but no package.json declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift CONTRIBUTING.md:64— CONTRIBUTING.md installs `Install` (`npm install # Install frontend deps`), but no package.json declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift CONTRIBUTING.md:64— CONTRIBUTING.md installs `frontend` (`npm install # Install frontend deps`), but no package.json declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift CONTRIBUTING.md:64— CONTRIBUTING.md installs `deps` (`npm install # Install frontend deps`), but no package.json declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift CONTRIBUTING.md:269— CONTRIBUTING.md links to `docs/VERSIONING.md`, but `docs/VERSIONING.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift CONTRIBUTING.md:554— CONTRIBUTING.md installs `package-name` (`npm install package-name`), but no package.json declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift CONTRIBUTING.md:699— CONTRIBUTING.md links to `docs/PRE_COMMIT_HOOKS.md`, but `docs/PRE_COMMIT_HOOKS.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/architecture.md:605— docs/architecture.md names `src/flock/store.py`, but no file or folder `src/flock/store.py` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/architecture.md:643— docs/architecture.md names `storage/sqlite/sqlite_store.py`, but no file or folder `storage/sqlite/sqlite_store.py` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/architecture.md:651— docs/architecture.md names `storage/in_memory/memory_store.py`, but no file or folder `storage/in_memory/memory_store.py` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/architecture.md:678— docs/architecture.md names `src/flock/engines/base.py`, but no file or folder `src/flock/engines/base.py` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/architecture.md:732— docs/architecture.md names `dspy/tool_executor.py`, but no file or folder `dspy/tool_executor.py` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/architecture.md:733— docs/architecture.md names `dspy/prompt_builder.py`, but no file or folder `dspy/prompt_builder.py` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/architecture.md:1014— docs/architecture.md names `docs/refactor/breaking_changes.md`, but no file or folder `docs/refactor/breaking_changes.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/about/contributing.md:75— docs/about/contributing.md installs `#` (`npm install # Install frontend deps`), but no package.json declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/about/contributing.md:75— docs/about/contributing.md installs `Install` (`npm install # Install frontend deps`), but no package.json declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/about/contributing.md:75— docs/about/contributing.md installs `frontend` (`npm install # Install frontend deps`), but no package.json declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/about/contributing.md:75— docs/about/contributing.md installs `deps` (`npm install # Install frontend deps`), but no package.json declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/about/contributing.md:445— docs/about/contributing.md installs `package-name` (`npm install package-name`), but no package.json declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/guides/components.md:783— docs/guides/components.md links to `../reference/api/components.md`, but `docs/reference/api/components.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/guides/local-models.md:39— docs/guides/local-models.md documents the environment variable `OLLAMA_API_BASE`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/guides/mcp-roots.md:415— docs/guides/mcp-roots.md links to `./mcp-architecture.md`, but `docs/guides/mcp-architecture.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/guides/mcp-roots.md:416— docs/guides/mcp-roots.md links to `./agent-builder.md`, but `docs/guides/agent-builder.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/guides/orchestrator-components.md:731— docs/guides/orchestrator-components.md links to `../guides/custom-engines.md`, but `docs/guides/custom-engines.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/guides/orchestrator-components.md:734— docs/guides/orchestrator-components.md links to `../reference/api/orchestrator_component.md`, but `docs/reference/api/orchestrator_component.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
Duplicated predicate src/flock/frontend/src/components/details/MessageDetailWindow.tsx:301— `artifact.visibility_kind || artifact.visibility?.kind || 'Unknown'` appears character-identically in 2 files — src/flock/frontend/src/components/details/MessageDetailWindow.tsx, src/flock/frontend/src/components/modules/HistoricalArtifactsModule.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 src/flock/frontend/src/components/filters/CorrelationIDFilter.tsx:31— `containerRef.current && !containerRef.current.contains(event.target as Node)` appears character-identically in 2 files — src/flock/frontend/src/components/filters/CorrelationIDFilter.tsx, src/flock/frontend/src/components/settings/MultiSelect.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 src/flock/frontend/src/components/modules/HistoricalArtifactsModule.tsx:32— `range.preset === 'custom' && range.start && range.end` appears character-identically in 2 files — src/flock/frontend/src/components/modules/HistoricalArtifactsModule.tsx, src/flock/frontend/src/store/filterStore.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/flock/frontend/src/components/graph/AgentNode.tsx:98— `spec.type === 'datetime' && spec.datetime` appears character-identically in 2 files — src/flock/frontend/src/components/graph/AgentNode.tsx, src/flock/frontend/src/components/graph/ScheduledAgentDisplay.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 src/flock/frontend/src/components/graph/AgentNode.tsx:86— `spec.type === 'interval' && spec.interval` appears character-identically in 2 files — src/flock/frontend/src/components/graph/AgentNode.tsx, src/flock/frontend/src/components/graph/ScheduledAgentDisplay.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 src/flock/mcp/servers/sse/flock_sse_server.py:99— `"auth" in additional_params and isinstance( additional_params.get("auth"), httpx.Auth )` appears character-identically in 2 files — src/flock/mcp/servers/sse/flock_sse_server.py, src/flock/mcp/servers/streamable_http/flock_streamable_http_server.py. 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 src/flock/core/orchestrator.py:904— `artifacts and artifacts[0].correlation_id` appears character-identically in 2 files — src/flock/core/orchestrator.py, src/flock/orchestrator/context_builder.py. 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 REDACTED:429— `bool(context_history) and self.should_use_context(inputs)` appears character-identically in 2 files — REDACTED, src/flock/integrations/openclaw/engine.py. 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 src/flock/core/agent.py:219— `component.name or component.__class__.__name__` appears character-identically in 3 files — src/flock/core/agent.py, src/flock/core/orchestrator.py, src/flock/orchestrator/component_runner.py. 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 src/flock/components/server/artifacts/artifacts_component.py:605— `filters.start is None and filters.end is None` appears character-identically in 3 files — src/flock/components/server/artifacts/artifacts_component.py, src/flock/core/store.py, src/flock/storage/dapr/dapr_state_blackboard_store.py. 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 src/flock/engines/dspy/streaming_executor.py:425— `getattr(ctx, "correlation_id", "") or ""` appears character-identically in 2 files — src/flock/engines/dspy/streaming_executor.py, src/flock/integrations/openclaw/engine.py. 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 src/flock/api/graph_builder.py:361— `hasattr(agent, "schedule_spec") and agent.schedule_spec` appears character-identically in 3 files — src/flock/api/graph_builder.py, src/flock/components/orchestrator/scheduling/timer.py, src/flock/core/orchestrator.py. 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 src/flock/core/artifacts.py:48— `isinstance(value, dict) or type(value) is Visibility` appears character-identically in 2 files — src/flock/core/artifacts.py, src/flock/core/visibility.py. 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 src/flock/logging/formatters/theme_builder.py:295— `isinstance(value, str) and "\n" in value` appears character-identically in 2 files — src/flock/logging/formatters/theme_builder.py, src/flock/logging/formatters/themed_formatter.py. 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 src/flock/api/graph_builder.py:1017— `not accumulator or not accumulator.artifacts` appears character-identically in 2 files — src/flock/api/graph_builder.py, src/flock/components/server/control/helpers.py. 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 scripts/bump_version.py:259— `not backend_changed and not frontend_changed` appears character-identically in 2 files — scripts/bump_version.py, scripts/check_version_bump.py. 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 src/flock/application/types.py:29— `not isinstance(value, str) or not value.strip()` appears character-identically in 2 files — src/flock/application/types.py, src/flock/utils/visibility_utils.py. 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 src/flock/api/graph_builder.py:1258— `not subscription.join and not subscription.batch` appears character-identically in 2 files — src/flock/api/graph_builder.py, src/flock/components/server/control/helpers.py. 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 src/flock/logging/telemetry_exporter/duckdb_exporter.py:182— `span.parent and span.parent.span_id != 0` appears character-identically in 2 files — src/flock/logging/telemetry_exporter/duckdb_exporter.py, src/flock/logging/telemetry_exporter/file_exporter.py. 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.
Orphaned file src/flock/components/server/auth/auth_component.py:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/flock/components/server/middleware/middleware_component.py:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/flock/components/server/cors/cors_component.py:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/flock/components/agent/guard.py:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/flock/mcp/types/handlers.py:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/flock/components/server/models/models.py:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/flock/mcp/types/factories.py:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/flock/mcp/types/callbacks.py:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Silent fallback default in catch src/flock/core/agent.py:497— `_resolve_engines` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch src/flock/core/agent.py:523— `_resolve_utilities` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch src/flock/engines/dspy/streaming_executor.py:86— `_make_listeners` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch src/flock/integrations/openclaw/streaming.py:221— `_parse_json` swallows every exception into `return {}` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch src/flock/semantic/context_provider.py:101— `get_context` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch src/flock/frontend/src/components/graph/ScheduledAgentDisplay.tsx:72— `formatRelativeTime` (in `ScheduledAgentDisplay`) swallows every exception into `return 'Unknown'` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Mock-dominated test: should pass filters from filterStore to backend src/flock/frontend/src/store/graphStore.test.ts:127— This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should update filter facets from backend statistics src/flock/frontend/src/store/graphStore.test.ts:178— This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Fat interface: SettingsState (20 required operations) src/flock/frontend/src/store/settingsStore.ts:11— `SettingsState` declares 20 required operations: `setShowFilters`, `setShowControls`, `setShowSettings`, `setEdgeType`, `setEdgeStrokeWidth`, `setEdgeAnimation`, `setShowEdgeLabels`, `setTheme`, `setAgentIdleColor`, `setAgentActiveColor`, `setAgentErrorColor`, `setNodeShadow`, `setShowStatusPulse`, `setCompactNodeView`, `setLayoutDirection`, `setNodeSpacing`, `setRankSpacing`, `setDebugMode`, `setPerformanceMode`, `resetToDefaults`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Thin authorization enforcement — Only 1 place(s) refuse an unauthorized caller — too few to demonstrate default-deny across handlers.
D20 · ADR Quality· ADR has no Consequences section · ×1
ADR has no Consequences section openspec/changes/archive/2026-02-17-openclaw-multi-output-envelope/design.md:1— openspec/changes/archive/2026-02-17-openclaw-multi-output-envelope/design.md has no Consequences section (a heading such as `## Consequences`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 2 of 2 project(s) overshoot their size bounds, lowering Project Cohesion to 0.0/10. The most over is `(repository root)` (58218 LoC, 916 module-visible types across 74 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
D34 · Knowledge Freshness· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 8 of 203 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated and example/demo trees and test files identified by path convention, largest first; 203 of the 289 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: src/flock/components/server/auth/auth_component.py, src/flock/components/server/middleware/middleware_component.py, src/flock/components/server/cors/cors_component.py, src/flock/components/agent/guard.py, src/flock/mcp/types/handlers.py, src/flock/components/server/models/models.py, src/flock/mcp/types/factories.py, src/flock/mcp/types/callbacks.py. Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
M2 · Architecture documentation· ADRs not easily discoverable · ×1
ADRs not easily discoverable — 2 ADR-shaped document(s) detected by content — `examples/15-decisions/README.md`, `openspec/changes/archive/2026-02-17-openclaw-multi-output-envelope/design.md`. They are not under a conventional ADR folder (docs/adr/) and are not named NNNN-title.md, and this check found them by their decision signature rather than by where they live — so a reader who does not already know these paths has no route to them. Detected by content signature only: records kept outside the repository, or written without a Status/Decision/Consequences shape, are not visible to this check and are not counted here.
No SAST — No static application security testing detected. For this repository's stack, add bandit, `semgrep --config=p/python`, or CodeQL's python pack as a CI step. What was searched, so you can tell an absence from a miss: the 4100 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.
R7 · Dead Code· Unused export 'applyDagreLayout' · ×1
Unused export 'applyDagreLayout' src/flock/frontend/src/services/layout.ts:598— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'getThemePreview' · ×1
Unused export 'getThemePreview' src/flock/frontend/src/services/themeApplicator.ts:129— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'CorrelationGroupUpdatedEvent' · ×1
Unused export 'CorrelationGroupUpdatedEvent' src/flock/frontend/src/types/graph.ts:98— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'BatchItemAddedEvent' · ×1
Unused export 'BatchItemAddedEvent' src/flock/frontend/src/types/graph.ts:114— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'startRenderMeasure' · ×1
Unused export 'startRenderMeasure' src/flock/frontend/src/utils/performance.ts:12— Nothing imports this binding — it is safe to review for removal.
X2 · Cancellation propagation· Not all async functions that make a request accept an AbortSignal · ×1
Not all async functions that make a request accept an AbortSignal — Only 0/17 async functions that make a cancellable request (fetch, axios, ky, ofetch) 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.
X23 · Unguarded diagnostic materialisation· Diagnostic log message is built whether or not it is wanted · ×1
Diagnostic log message is built whether or not it is wanted src/flock/mcp/client.py:682— `debug` at line 682 is called with an argument built by `[r.uri for r in self.current_roots]` (line 684), whose cost grows with the collection it walks. Python evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isEnabledFor(logging.DEBUG)` test, no debug flag, no `lambda` the logger calls only when the level is on.
Null assertions (`!`) reduce the strict null checking score — ~0.8 `!` null assertions per 1k TypeScript source lines — 14 assertion(s) across the 18133 source line(s) of the 80 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: src/flock/frontend/src/components/modules/TraceModuleJaeger.tsx (7), src/flock/frontend/src/components/graph/LogicOperationsDisplay.tsx (2), src/flock/frontend/src/services/layout.ts (2). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
Outdated: aiosqlite — `aiosqlite` is pinned to 0.21.0, but 0.22.1 is the current stable release on PyPI. An exact pin never moves on its own, so this repository installs 0.21.0 until the declaration is edited.
Outdated: dspy — `dspy` is pinned to 3.2.1, but 3.4.1 is the current stable release on PyPI. An exact pin never moves on its own, so this repository installs 3.2.1 until the declaration is edited.
Outdated: fastapi — `fastapi` is pinned to 0.143.0, but 0.161.0 is the current stable release on PyPI. An exact pin never moves on its own, so this repository installs 0.143.0 until the declaration is edited.
Outdated: litellm — `litellm` is pinned to 1.96.2, but 1.106.2 is the current stable release on PyPI. An exact pin never moves on its own, so this repository installs 1.96.2 until the declaration is edited.
Outdated: pydantic — `pydantic` is pinned to 2.12.5, but 2.14.1 is the current stable release on PyPI. An exact pin never moves on its own, so this repository installs 2.12.5 until the declaration is edited.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 1 file(s) — `src/flock/core/artifacts.py` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a165b9-bd7c-7985-8f56-409d48d5b269 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 55 · Warnings: 478 · Recommendations: 95 · Info: 5 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 22-10-2026 @ 22:27 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.