Public report — arroyo, published 30 Sep 2026.
Concrete security findings (which rule fired, in which file, on which line; CVE IDs, secret matches,
dependency versions) are REDACTED in this version; ask the repo owner for the full report.
Public
Codebase surveyMeasured under the Code Assurance Index · rubric rubric-2026.09.18 (frozen) · verify this surveyFiledcd_e0f01a972d5f4c92b72ebd4bf7687559
Filed 30 September 2026, 05:34 UTC
Public
Medium · 89,547 LoC · 27 projects · rebuild ~0.6 person-years · weakest lens: Accessibility (39%)
Findings by grade
74 critical505 serious55 minor38 could not be resolved — could be critical — see Limitations
This survey was produced by
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
30 September 2026, 05:27 UTC
A measurement, not a certificate. The Code Assurance Index does not certify,
approve or guarantee this codebase; it records a reproducible number and the evidence it was computed from. The
standard is authored by Canine Development, who also build Watchdog — its only implementation today. That is said
here so the number is checked rather than believed.
Grounded in facts. Every number here is computed, not narrated — reproducible, tool-backed, and traceable to a line of code. How to trust this ▸
571findings with an exact file:lineof 634 — the remainder are repo-wide signals (a dimension-level measurement, not a single line); open any file:line and verify
62/133dimensions across the health lenses89547 LoC · 27 projects — wide & deep
⚠ A critical security finding caps this grade — resolve it before relying on the score below; see the Security lens.
Preview (pre-1.0). This repo hasn't declared a stable release, so it's judged against a relaxed, pre-production bar.
The system holds a 49% health score, placing it in the At Risk category. While the core code is robust, significant gaps in accessibility and operational readiness create tangible business exposure. This is a medium-sized asset, representing a rebuild effort of roughly 0.6 person-years or €84,000, meaning the value tied up here is substantial enough to warrant immediate, targeted intervention rather than wholesale replacement.
The most critical vulnerability lies in Accessibility, which scores only 39%. For a system of this size, failing to meet accessibility standards is not merely a technical debt issue; it is a direct legal and reputational risk that can exclude users and invite compliance penalties. The current implementation lacks basic text alternatives for images and programmatic labels for controls, creating a barrier to entry for users relying on assistive technologies. Remediation here offers the highest return on investment, as fixing these foundational elements protects the brand and ensures broader market reach with minimal engineering effort.
Secondary concerns involve Operational Readiness and Architecture. With scores of 58% and 65% respectively, the system lacks the observability and structural clarity needed for safe, rapid changes. While the code itself is healthy (84%), the lack of maturity (54%) means new teams may struggle to navigate the logic, increasing the cost of future maintenance and the likelihood of defects during updates. The absence of measured data on domain modeling and event-driven patterns further obscures the full picture, suggesting that some areas of the system remain unknown rather than confirmed as secure.
Strengths include a clean codebase with no boilerplate waste and perfect scores in performance and event sourcing, indicating that the core logic is efficient and well-structured. However, these strengths are undermined by the accessibility gaps. The first action must be to enforce accessibility in the toolchain by adding linting and automated testing for screen reader compatibility. This low-effort, high-impact step will immediately reduce legal exposure and set a standard for future development, ensuring that speed and reliability do not come at the cost of inclusivity.
How the score is built — each lens's share of the headlineWidth is the lens's weight in the worst-heaviest fold (the weakest area pulls hardest); colour is that lens's own band. A lens fixes the score in proportion to its width.
D22 · Inconsistent parameter naming for identical signatures. Most connectors use `options` (plural), while ConfluentConnector uses `opts` (abbreviated).
D22 · Inconsistent parameter naming for identical signatures. Most connectors use `options` (plural), while ConfluentConnector uses `opts` (abbreviated). Note: ConfluentConnector does not expose `table_from_options`, but the inconsistency in `connection_from_options` is sufficient to flag the naming convention drift.
R2 · Complex function ConfigEntry (cyclomatic 13, cognitive 14) webui/src/components/ConfigViewer.tsx
P7 · Outbound HTTP without resilience crates/arroyo-connectors/src/filesystem/iceberg.rs
P7 · Outbound HTTP without resilience crates/arroyo-server-common/src/lib.rs
AC2 · <Select> field component without a label webui/src/components/ConfigViewer.tsx
A full-fidelity diff against the previous run's complete recorded findings — line-move tolerant: a finding that only shifted line counts as unchanged, only genuinely new titles/files surface here.
0.7× (at 49% quality) — the last 20% of quality is most of the work
Size & shape
Medium · effort split not classified (source measured from disk; the effort-tier breakdown is a C#-only syntax walk)
This codebase represents roughly ~0.6 person-years of build effort (about ~€84,000 to rebuild). Its weakest lens is Accessibility at 39% — the part of that asset most exposed by the findings below.
How we model this: boilerplate at a scaffolding rate + logic × domain Standard (×1.0) — standard service × a 0.7× quality factor, at €60–95/h; indicative, ±~30% · size measured directly from source · effort from total production LoC as straight-line logic (the tier split is a C#-only syntax walk), a conservative lower bound. Indicative only — most sensitive to the hourly rate and the domain tier (both tunable in config).
Top priorities
The highest-leverage moves; the full ranked list is in the Roadmap below.
1
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI.
Value concentrated against a weak lens · High · Value at risk
This is a Medium asset (~0.6 person-years to rebuild), and its weakest lens is Accessibility at 39%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.
→ Direct remediation budget at Accessibility first — highest risk-reduction per euro on an asset this size.
Highest-leverage move · Medium · Leverage
Of everything flagged, the best return on effort is: Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video. The rest can wait behind it.
Evidence: priority ranking: top of 5 ranked by impact/effort
→ Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways — a layering smell or cycle. A clean layered graph has none.
Architecture — module dependency matrix
Rows and columns are the same modules, ordered so that a module only depends on ones above it. A cell means the row depends on the column, and its number is how many type pairs create that dependency. Read one thing: is anything above the diagonal? A mark there is a dependency cycle. (A cycle is all this shows — an unusual but cycle-free dependency sits below the diagonal like any other.)
271 modules, 583 dependencies. 5 dependency cycles across 13 modules, marked above the diagonal.
Showing the 40 most-connected modules; 231 more are not drawn.
Module dependency matrix. The row depends on the column; the number is how many type pairs create the dependency. A cell above the diagonal is part of a dependency cycle.
arroyo_storage uses arroyo_state_protocol.types. Changing arroyo_state_protocol.types can break arroyo_storage, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
10→8 arroyo_connectors.filesystem.config depends on arroyo_rpc✕
Type pairs
29 distinct (type in arroyo_connectors.filesystem.config → type in arroyo_rpc) references. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
arroyo_controller.states uses arroyo_server_common.shutdown. Changing arroyo_server_common.shutdown can break arroyo_controller.states, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
13→11 arroyo_controller.states depends on arroyo_controller✕
Type pairs
9 distinct (type in arroyo_controller.states → type in arroyo_controller) references.
arroyo_operator.connector uses arroyo_rpc.api_types.connections. Changing arroyo_rpc.api_types.connections can break arroyo_operator.connector, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
15→12 arroyo_rpc.df depends on arroyo_rpc.api_types.connections✕
Type pairs
1 distinct (type in arroyo_rpc.df → type in arroyo_rpc.api_types.connections) reference.
arroyo_connectors.filesystem uses arroyo_connectors.filesystem.config. Changing arroyo_connectors.filesystem.config can break arroyo_connectors.filesystem, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
16→12 arroyo_connectors.filesystem depends on arroyo_rpc.api_types.connections✕
Type pairs
3 distinct (type in arroyo_connectors.filesystem → type in arroyo_rpc.api_types.connections) references.
arroyo_connectors.filesystem uses arroyo_rpc.api_types.connections. Changing arroyo_rpc.api_types.connections can break arroyo_connectors.filesystem, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
16→14 arroyo_connectors.filesystem depends on arroyo_operator.connector✕
Type pairs
1 distinct (type in arroyo_connectors.filesystem → type in arroyo_operator.connector) reference.
arroyo_connectors.filesystem uses arroyo_operator.connector. Changing arroyo_operator.connector can break arroyo_connectors.filesystem, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
17→5 arroyo_connectors.kafka depends on arroyo_rpc.formats✕
Type pairs
1 distinct (type in arroyo_connectors.kafka → type in arroyo_rpc.formats) reference.
arroyo_connectors.kafka uses arroyo_rpc.api_types.connections. Changing arroyo_rpc.api_types.connections can break arroyo_connectors.kafka, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
17→14 arroyo_connectors.kafka depends on arroyo_operator.connector✕
Type pairs
1 distinct (type in arroyo_connectors.kafka → type in arroyo_operator.connector) reference.
arroyo_planner.tables uses arroyo_rpc.api_types.connections. Changing arroyo_rpc.api_types.connections can break arroyo_planner.tables, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
19→14 arroyo_planner.tables depends on arroyo_operator.connector✕
Type pairs
1 distinct (type in arroyo_planner.tables → type in arroyo_operator.connector) reference.
arroyo_state.tables.expiring_time_key_map uses arroyo_rpc.config. Changing arroyo_rpc.config can break arroyo_state.tables.expiring_time_key_map, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
22→4 arroyo_state.tables.expiring_time_key_map depends on arroyo_types✕
Type pairs
2 distinct (type in arroyo_state.tables.expiring_time_key_map → type in arroyo_types) references.
arroyo_state.tables.expiring_time_key_map uses arroyo_types. Changing arroyo_types can break arroyo_state.tables.expiring_time_key_map, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
22→8 arroyo_state.tables.expiring_time_key_map depends on arroyo_rpc✕
Type pairs
2 distinct (type in arroyo_state.tables.expiring_time_key_map → type in arroyo_rpc) references.
arroyo_state.tables.expiring_time_key_map uses arroyo_planner.tables. Changing arroyo_planner.tables can break arroyo_state.tables.expiring_time_key_map, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
23→4 arroyo_worker.job_controller.model depends on arroyo_types✕
Type pairs
3 distinct (type in arroyo_worker.job_controller.model → type in arroyo_types) references.
arroyo_worker.job_controller.model uses arroyo_state_protocol.types. Changing arroyo_state_protocol.types can break arroyo_worker.job_controller.model, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
23→18 arroyo_worker.job_controller.model depends on arroyo_datastream.logical✕
Type pairs
1 distinct (type in arroyo_worker.job_controller.model → type in arroyo_datastream.logical) reference.
arroyo_worker.job_controller.model uses arroyo_datastream.logical. Changing arroyo_datastream.logical can break arroyo_worker.job_controller.model, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
24→1 arroyo_api.pipelines depends on arroyo_rpc.config✕
Type pairs
1 distinct (type in arroyo_api.pipelines → type in arroyo_rpc.config) reference.
arroyo_worker.job_controller uses arroyo_worker.job_controller.model. Changing arroyo_worker.job_controller.model can break arroyo_worker.job_controller, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
28→2 arroyo_operator.context depends on arroyo_rpc.errors✕
Type pairs
2 distinct (type in arroyo_operator.context → type in arroyo_rpc.errors) references.
arroyo_worker.job_controller.controller uses arroyo_server_common.shutdown. Changing arroyo_server_common.shutdown can break arroyo_worker.job_controller.controller, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
30→6 arroyo_worker.job_controller.controller depends on arroyo_state_protocol.types✕
Type pairs
1 distinct (type in arroyo_worker.job_controller.controller → type in arroyo_state_protocol.types) reference.
arroyo_worker.job_controller.controller uses arroyo_state_protocol.types. Changing arroyo_state_protocol.types can break arroyo_worker.job_controller.controller, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
30→11 arroyo_worker.job_controller.controller depends on arroyo_controller✕
Type pairs
1 distinct (type in arroyo_worker.job_controller.controller → type in arroyo_controller) reference.
arroyo_worker.job_controller.controller uses arroyo_controller. Changing arroyo_controller can break arroyo_worker.job_controller.controller, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
30→18 arroyo_worker.job_controller.controller depends on arroyo_datastream.logical✕
Type pairs
1 distinct (type in arroyo_worker.job_controller.controller → type in arroyo_datastream.logical) reference.
arroyo_worker.job_controller.controller uses arroyo_datastream.logical. Changing arroyo_datastream.logical can break arroyo_worker.job_controller.controller, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
30→23 arroyo_worker.job_controller.controller depends on arroyo_worker.job_controller.model✕
Type pairs
1 distinct (type in arroyo_worker.job_controller.controller → type in arroyo_worker.job_controller.model) reference.
arroyo_worker.job_controller.controller uses arroyo_worker.job_controller.model. Changing arroyo_worker.job_controller.model can break arroyo_worker.job_controller.controller, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
30→27 arroyo_worker.job_controller.controller depends on arroyo_worker.job_controller✕
Type pairs
2 distinct (type in arroyo_worker.job_controller.controller → type in arroyo_worker.job_controller) references.
arroyo_worker.job_controller.controller uses arroyo_worker.job_controller. Changing arroyo_worker.job_controller can break arroyo_worker.job_controller.controller, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
31→4 arroyo_connectors.filesystem.sink.two_phase_committer depends on arroyo_types✕
Type pairs
2 distinct (type in arroyo_connectors.filesystem.sink.two_phase_committer → type in arroyo_types) references.
arroyo_connectors.filesystem.sink.two_phase_committer uses arroyo_types. Changing arroyo_types can break arroyo_connectors.filesystem.sink.two_phase_committer, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
31→20 arroyo_connectors.filesystem.sink.two_phase_committer depends on arroyo_operator.operator✕
Type pairs
1 distinct (type in arroyo_connectors.filesystem.sink.two_phase_committer → type in arroyo_operator.operator) reference.
arroyo_connectors.filesystem.sink.two_phase_committer uses arroyo_operator.operator. Changing arroyo_operator.operator can break arroyo_connectors.filesystem.sink.two_phase_committer, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
31→28 arroyo_connectors.filesystem.sink.two_phase_committer depends on arroyo_operator.context✕
Type pairs
2 distinct (type in arroyo_connectors.filesystem.sink.two_phase_committer → type in arroyo_operator.context) references.
arroyo_connectors.filesystem.sink.two_phase_committer uses arroyo_operator.context. Changing arroyo_operator.context can break arroyo_connectors.filesystem.sink.two_phase_committer, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
32→5 arroyo_connectors.filesystem.source depends on arroyo_rpc.formats✕
Type pairs
3 distinct (type in arroyo_connectors.filesystem.source → type in arroyo_rpc.formats) references.
arroyo_connectors.filesystem.source uses arroyo_rpc.formats. Changing arroyo_rpc.formats can break arroyo_connectors.filesystem.source, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
32→8 arroyo_connectors.filesystem.source depends on arroyo_rpc✕
Type pairs
1 distinct (type in arroyo_connectors.filesystem.source → type in arroyo_rpc) reference.
arroyo_connectors.filesystem.source uses arroyo_connectors.filesystem.config. Changing arroyo_connectors.filesystem.config can break arroyo_connectors.filesystem.source, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
32→20 arroyo_connectors.filesystem.source depends on arroyo_operator.operator✕
Type pairs
1 distinct (type in arroyo_connectors.filesystem.source → type in arroyo_operator.operator) reference.
arroyo_connectors.filesystem.source uses arroyo_operator.operator. Changing arroyo_operator.operator can break arroyo_connectors.filesystem.source, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
32→25 arroyo_connectors.filesystem.source depends on arroyo_operator✕
Type pairs
1 distinct (type in arroyo_connectors.filesystem.source → type in arroyo_operator) reference.
arroyo_connectors.filesystem.source uses arroyo_operator.context. Changing arroyo_operator.context can break arroyo_connectors.filesystem.source, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
33→4 arroyo_connectors.redis.sink depends on arroyo_types✕
Type pairs
1 distinct (type in arroyo_connectors.redis.sink → type in arroyo_types) reference.
arroyo_connectors.filesystem.sink uses arroyo_connectors.filesystem.config. Changing arroyo_connectors.filesystem.config can break arroyo_connectors.filesystem.sink, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
35→16 arroyo_connectors.filesystem.sink depends on arroyo_connectors.filesystem✕
Type pairs
2 distinct (type in arroyo_connectors.filesystem.sink → type in arroyo_connectors.filesystem) references.
arroyo_connectors.filesystem.sink uses arroyo_connectors.filesystem. Changing arroyo_connectors.filesystem can break arroyo_connectors.filesystem.sink, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
35→28 arroyo_connectors.filesystem.sink depends on arroyo_operator.context✕
Type pairs
1 distinct (type in arroyo_connectors.filesystem.sink → type in arroyo_operator.context) reference.
arroyo_connectors.filesystem.sink uses arroyo_operator.context. Changing arroyo_operator.context can break arroyo_connectors.filesystem.sink, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
35→31 arroyo_connectors.filesystem.sink depends on arroyo_connectors.filesystem.sink.two_phase_committer✕
Type pairs
3 distinct (type in arroyo_connectors.filesystem.sink → type in arroyo_connectors.filesystem.sink.two_phase_committer) references.
arroyo_connectors.filesystem.sink uses arroyo_connectors.filesystem.sink.two_phase_committer. Changing arroyo_connectors.filesystem.sink.two_phase_committer can break arroyo_connectors.filesystem.sink, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
36→3 arroyo_worker depends on arroyo_server_common.shutdown✕
Type pairs
3 distinct (type in arroyo_worker → type in arroyo_server_common.shutdown) references.
arroyo_connectors.filesystem.sink.local uses arroyo_rpc.errors. Changing arroyo_rpc.errors can break arroyo_connectors.filesystem.sink.local, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
37→4 arroyo_connectors.filesystem.sink.local depends on arroyo_types✕
Type pairs
1 distinct (type in arroyo_connectors.filesystem.sink.local → type in arroyo_types) reference.
arroyo_connectors.filesystem.sink.local uses arroyo_rpc.formats. Changing arroyo_rpc.formats can break arroyo_connectors.filesystem.sink.local, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
37→10 arroyo_connectors.filesystem.sink.local depends on arroyo_connectors.filesystem.config✕
Type pairs
4 distinct (type in arroyo_connectors.filesystem.sink.local → type in arroyo_connectors.filesystem.config) references.
arroyo_connectors.filesystem.sink.local uses arroyo_connectors.filesystem.config. Changing arroyo_connectors.filesystem.config can break arroyo_connectors.filesystem.sink.local, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
37→16 arroyo_connectors.filesystem.sink.local depends on arroyo_connectors.filesystem✕
Type pairs
1 distinct (type in arroyo_connectors.filesystem.sink.local → type in arroyo_connectors.filesystem) reference.
arroyo_connectors.filesystem.sink.local uses arroyo_connectors.filesystem. Changing arroyo_connectors.filesystem can break arroyo_connectors.filesystem.sink.local, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
37→28 arroyo_connectors.filesystem.sink.local depends on arroyo_operator.context✕
Type pairs
1 distinct (type in arroyo_connectors.filesystem.sink.local → type in arroyo_operator.context) reference.
arroyo_connectors.filesystem.sink.local uses arroyo_operator.context. Changing arroyo_operator.context can break arroyo_connectors.filesystem.sink.local, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
37→31 arroyo_connectors.filesystem.sink.local depends on arroyo_connectors.filesystem.sink.two_phase_committer✕
Type pairs
2 distinct (type in arroyo_connectors.filesystem.sink.local → type in arroyo_connectors.filesystem.sink.two_phase_committer) references.
arroyo_connectors.filesystem.sink.local uses arroyo_connectors.filesystem.sink.two_phase_committer. Changing arroyo_connectors.filesystem.sink.two_phase_committer can break arroyo_connectors.filesystem.sink.local, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
37→35 arroyo_connectors.filesystem.sink.local depends on arroyo_connectors.filesystem.sink✕
Type pairs
2 distinct (type in arroyo_connectors.filesystem.sink.local → type in arroyo_connectors.filesystem.sink) references.
arroyo_connectors.filesystem.sink.local uses arroyo_connectors.filesystem.sink. Changing arroyo_connectors.filesystem.sink can break arroyo_connectors.filesystem.sink.local, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
38→8 arroyo_connectors.filesystem.sink.v2.checkpoint depends on arroyo_rpc✕
Type pairs
1 distinct (type in arroyo_connectors.filesystem.sink.v2.checkpoint → type in arroyo_rpc) reference.
arroyo_connectors.filesystem.sink.v2.checkpoint uses arroyo_rpc. Changing arroyo_rpc can break arroyo_connectors.filesystem.sink.v2.checkpoint, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
38→35 arroyo_connectors.filesystem.sink.v2.checkpoint depends on arroyo_connectors.filesystem.sink✕
Type pairs
2 distinct (type in arroyo_connectors.filesystem.sink.v2.checkpoint → type in arroyo_connectors.filesystem.sink) references.
arroyo_connectors.filesystem.sink.v2.checkpoint uses arroyo_connectors.filesystem.sink. Changing arroyo_connectors.filesystem.sink can break arroyo_connectors.filesystem.sink.v2.checkpoint, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
39→9 arroyo_connectors.filesystem.sink.v2.open_file depends on arroyo_storage✕
Type pairs
2 distinct (type in arroyo_connectors.filesystem.sink.v2.open_file → type in arroyo_storage) references.
arroyo_connectors.filesystem.sink.v2.open_file uses arroyo_storage. Changing arroyo_storage can break arroyo_connectors.filesystem.sink.v2.open_file, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
39→31 arroyo_connectors.filesystem.sink.v2.open_file depends on arroyo_connectors.filesystem.sink.two_phase_committer✕
Type pairs
1 distinct (type in arroyo_connectors.filesystem.sink.v2.open_file → type in arroyo_connectors.filesystem.sink.two_phase_committer) reference.
arroyo_connectors.filesystem.sink.v2.open_file uses arroyo_connectors.filesystem.sink.two_phase_committer. Changing arroyo_connectors.filesystem.sink.two_phase_committer can break arroyo_connectors.filesystem.sink.v2.open_file, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
39→35 arroyo_connectors.filesystem.sink.v2.open_file depends on arroyo_connectors.filesystem.sink✕
Type pairs
3 distinct (type in arroyo_connectors.filesystem.sink.v2.open_file → type in arroyo_connectors.filesystem.sink) references.
arroyo_connectors.filesystem.sink.v2.open_file uses arroyo_connectors.filesystem.sink. Changing arroyo_connectors.filesystem.sink can break arroyo_connectors.filesystem.sink.v2.open_file, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
39→38 arroyo_connectors.filesystem.sink.v2.open_file depends on arroyo_connectors.filesystem.sink.v2.checkpoint✕
Type pairs
3 distinct (type in arroyo_connectors.filesystem.sink.v2.open_file → type in arroyo_connectors.filesystem.sink.v2.checkpoint) references.
arroyo_connectors.filesystem.sink.v2.open_file uses arroyo_connectors.filesystem.sink.v2.checkpoint. Changing arroyo_connectors.filesystem.sink.v2.checkpoint can break arroyo_connectors.filesystem.sink.v2.open_file, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
39→40 arroyo_connectors.filesystem.sink.v2.open_file depends on arroyo_connectors.filesystem.sink.v2cycle✕
Type pairs
1 distinct (type in arroyo_connectors.filesystem.sink.v2.open_file → type in arroyo_connectors.filesystem.sink.v2) reference.
arroyo_connectors.filesystem.sink.v2.open_file uses arroyo_connectors.filesystem.sink.v2. Changing arroyo_connectors.filesystem.sink.v2 can break arroyo_connectors.filesystem.sink.v2.open_file, not the reverse.
Position
Above the diagonal — a cycle. Neither module can be changed, tested or deployed independently until one of these dependencies goes.
40→4 arroyo_connectors.filesystem.sink.v2 depends on arroyo_types✕
Type pairs
4 distinct (type in arroyo_connectors.filesystem.sink.v2 → type in arroyo_types) references.
arroyo_connectors.filesystem.sink.v2 uses arroyo_rpc.formats. Changing arroyo_rpc.formats can break arroyo_connectors.filesystem.sink.v2, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
40→9 arroyo_connectors.filesystem.sink.v2 depends on arroyo_storage✕
Type pairs
1 distinct (type in arroyo_connectors.filesystem.sink.v2 → type in arroyo_storage) reference.
arroyo_connectors.filesystem.sink.v2 uses arroyo_connectors.filesystem.config. Changing arroyo_connectors.filesystem.config can break arroyo_connectors.filesystem.sink.v2, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
40→16 arroyo_connectors.filesystem.sink.v2 depends on arroyo_connectors.filesystem✕
Type pairs
2 distinct (type in arroyo_connectors.filesystem.sink.v2 → type in arroyo_connectors.filesystem) references.
arroyo_connectors.filesystem.sink.v2 uses arroyo_connectors.filesystem. Changing arroyo_connectors.filesystem can break arroyo_connectors.filesystem.sink.v2, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
40→20 arroyo_connectors.filesystem.sink.v2 depends on arroyo_operator.operator✕
Type pairs
1 distinct (type in arroyo_connectors.filesystem.sink.v2 → type in arroyo_operator.operator) reference.
arroyo_connectors.filesystem.sink.v2 uses arroyo_operator.operator. Changing arroyo_operator.operator can break arroyo_connectors.filesystem.sink.v2, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
40→28 arroyo_connectors.filesystem.sink.v2 depends on arroyo_operator.context✕
Type pairs
2 distinct (type in arroyo_connectors.filesystem.sink.v2 → type in arroyo_operator.context) references.
arroyo_connectors.filesystem.sink.v2 uses arroyo_operator.context. Changing arroyo_operator.context can break arroyo_connectors.filesystem.sink.v2, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
40→31 arroyo_connectors.filesystem.sink.v2 depends on arroyo_connectors.filesystem.sink.two_phase_committer✕
Type pairs
1 distinct (type in arroyo_connectors.filesystem.sink.v2 → type in arroyo_connectors.filesystem.sink.two_phase_committer) reference.
arroyo_connectors.filesystem.sink.v2 uses arroyo_connectors.filesystem.sink.two_phase_committer. Changing arroyo_connectors.filesystem.sink.two_phase_committer can break arroyo_connectors.filesystem.sink.v2, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
40→35 arroyo_connectors.filesystem.sink.v2 depends on arroyo_connectors.filesystem.sink✕
Type pairs
3 distinct (type in arroyo_connectors.filesystem.sink.v2 → type in arroyo_connectors.filesystem.sink) references.
arroyo_connectors.filesystem.sink.v2 uses arroyo_connectors.filesystem.sink. Changing arroyo_connectors.filesystem.sink can break arroyo_connectors.filesystem.sink.v2, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
40→38 arroyo_connectors.filesystem.sink.v2 depends on arroyo_connectors.filesystem.sink.v2.checkpoint✕
Type pairs
1 distinct (type in arroyo_connectors.filesystem.sink.v2 → type in arroyo_connectors.filesystem.sink.v2.checkpoint) reference.
arroyo_connectors.filesystem.sink.v2 uses arroyo_connectors.filesystem.sink.v2.checkpoint. Changing arroyo_connectors.filesystem.sink.v2.checkpoint can break arroyo_connectors.filesystem.sink.v2, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
40→39 arroyo_connectors.filesystem.sink.v2 depends on arroyo_connectors.filesystem.sink.v2.open_file✕
Type pairs
2 distinct (type in arroyo_connectors.filesystem.sink.v2 → type in arroyo_connectors.filesystem.sink.v2.open_file) references.
arroyo_connectors.filesystem.sink.v2 uses arroyo_connectors.filesystem.sink.v2.open_file. Changing arroyo_connectors.filesystem.sink.v2.open_file can break arroyo_connectors.filesystem.sink.v2, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
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
A06:2021 — Vulnerable & Outdated Components
59
High / Critical
A03:2021 — Injection
45
High / Critical
A05:2021 — Security Misconfiguration
12
High / Critical
Roadmap
First, address immediate accessibility gaps by adding text alternatives for media and programmatic labels for all form controls and buttons. Next, enforce these standards in the development toolchain by integrating accessibility linting and automated testing into the CI pipeline. Finally, ensure proper page structure by defining language, titles, and landmarks, and document the testing process in the README.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI.
Record significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree, with each file named `NNNN-title` in whatever markup those docs already use, is the most discoverable form).
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 — 74
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 — 505
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 — 55
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 38
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. 57 of 62 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 5 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 62 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, 571 of 634 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: test source is present (.rs) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.rs) and this repository declares a Cargo test suite (repository root, 52 test files), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
D44 Platform End-of-Life — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a REDACTED) is simply not read here yet.
AX6 Interface segregation — 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 is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
C1 Data Protection — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
C2 Access Controls — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
C3 Audit Trail — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
C4 Data Retention — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
C5 Data-Subject Rights — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
ED5 Idempotency — 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 finds retry-prone mutations by walking the repository's declared types, and NONE was loaded on this run, so it had nothing to look at. That is a limit of the analyzer's reach — it reads .NET projects — not a finding that this repository has no command handlers or message consumers.
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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
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.
X1 Async correctness — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X12 Unreachable branch — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X13 Undrained process stream — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X14 Bypassable address classification — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X15 Unvalidated length from an untrusted reader — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X16 Unfloored truncation loop — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X17 Uncapped recursion over a caller-supplied document — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X18 Disposal-pattern correctness — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X19 Unrestored process-global state — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X2 Cancellation propagation — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X20 Mistyped argument guard — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X21 Side-effecting pattern guard — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X22 Contradicted release guard — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X23 Unguarded diagnostic materialisation — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X24 Document value interpolated into markup unescaped — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X25 Inert configuration knob — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X26 Unsynchronised callback handoff — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X27 Collection changed while being enumerated — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X28 Index access outside its own emptiness guard — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X3 Exception handling — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X30 Support guard that admits what it rejects — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X4 Structured logging — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X5 Nullable reference types — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations: 3 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.
Limitations & what we did not check
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.
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.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality 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.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D40 Network Egress Confinement: Egress confinement is read from committed Kubernetes manifests — a policy applied out-of-band (cluster-default deny, a service mesh, or a cloud firewall/security group off-repo) is invisible, and a present NetworkPolicy is declared config, not proof the cluster admission-controller actually enforces it at runtime.
D41 Kernel & Syscall Confinement: Syscall/MAC confinement is read from committed manifests — a profile applied by a cluster-wide PodSecurity default or a mutating webhook off-repo isn't seen, and a declared seccomp/AppArmor profile is config presence, not proof the node's kernel actually loaded and enforced it.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
The LLM boundary
LLM-set scores this run (5): D19, D21, D22, 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.
40 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was CreatePipeline.CreatePipeline at 64. A further 12 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being arroyo_operator::udfs::scalar_none at 50 — they are counted neither in the figure above nor in this dimension's score. 9 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: crates/arroyo-operator/src/udfs.rs (arroyo_operator::udfs::scalar_none at 50), crates/arroyo-planner/src/types.rs (arroyo_planner::types::convert_simple_data_type at 31), crates/arroyo-api/src/jobs.rs (arroyo_api::jobs::get_action at 30), crates/arroyo-formats/src/avro/schema.rs (arroyo_formats::avro::schema::arrow_to_avro at 28), crates/arroyo-formats/src/json/mod.rs (arroyo_formats::json::field_to_kafka_json at 26), and 4 more not listed here. They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 32 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 arroyo_formats finding(s) in Cyclomatic Complexity — start with ser.rs, de.rs. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 WorkerJobController finding(s) in Cyclomatic Complexity — start with controller.rs (2). — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 arroyo_connectors finding(s) in Cyclomatic Complexity — start with metadata.rs (2). — One of this dimension's main actionable groups (2 warning-level).
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.
+ 65 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 IncrementalAggregatingFunc finding(s) in Cognitive Complexity — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 WorkerJobController finding(s) in Cognitive Complexity — start with controller.rs (2). — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 arroyo_api finding(s) in Cognitive Complexity — start with pipelines.rs (2). — One of this dimension's main actionable groups (2 warning-level).
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.3 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 32 FileTooLong finding(s) in God Classes — start with mod.rs (5), lib.rs (4), operator.rs (2). — One of this dimension's main actionable groups (32 warning-level).
Resolve the 23 MethodTooLong finding(s) in God Classes — start with mod.rs (6), tables.rs (2), model.rs (2). — One of this dimension's main actionable groups (23 warning-level).
Resolve the 18 FunctionTooLong finding(s) in God Classes — start with JsonForm.tsx (3), mod.rs (2), CreatePipeline.tsx. — One of this dimension's main actionable groups (18 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.
96 duplicated block group(s) detected. A further 3 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
+ 49 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 9 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with mod.rs (3), open_file.rs, sink.rs. — One of this dimension's main actionable groups (9 warning-level).
Resolve the 6 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with sliding_aggregating_window.rs (2), json.rs, mod.rs. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 5 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with source.rs, global_keyed_map.rs, pyarrow.rs. — One of this dimension's main actionable groups (5 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling7.9 / 10Strong✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
27 production modules (Cargo+npm), 0 dependency cycle(s), 1 unstable depended-on module(s). Read from the build's own module declarations; 7 module(s) off the main sequence, with abstractness counted on 22 of the 27 (the rest declare no modelled class or interface, export only macros, or have no source directory of their own).
Off the main sequence: arroyo-udf-common · ×7
Unstable project arroyo-api
What to do
Resolve the 7 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 1 Unstable project arroyo-api finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
274 test methods: 269 unit, 5 integration, 0 BDD, 0 e2e. The Rust suite contributes 274 `#[test]` function(s) across 52 file(s) declaring at least one; its unit/integration split is Cargo's own — 2 of those file(s) are integration-test targets under a crate's tests/ directory, and the rest are #[test] functions compiled into the crate they test.
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.
29 outdated, 0 yanked direct Cargo dependencies. Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
Outdated: arc-swap · ×29
What to do
Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
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.
Resolve the 5 Hotspot finding(s) in Churn × Complexity Hotspots — start with scheduling.rs, leader_running.rs, controller.rs. — One of this dimension's main actionable groups (5 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor8.6 / 10Strong✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
34 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is crates/arroyo-state-protocol/src/lib.rs. Counted over 232 of the 302 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1
Further sole-owners (lower concentration)
What to do
Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
94 deducted task-comment markers across 89547 LoC (0.1/KLoC) → score 9.8. 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 91 TodoComment finding(s) in Explicit Debt — start with mod.rs (21), lib.rs (10), session_aggregating_window.rs (7). — One of this dimension's main actionable groups (91 warning-level).
Resolve the 2 XxxComment finding(s) in Explicit Debt — start with pyarrow.rs, interpreter.rs. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 FixmeComment finding(s) in Explicit Debt — start with interpreter.rs. — One of this dimension's main actionable groups (1 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 gives a strong overview (what Arroyo is and its main value proposition), links to docs, releases, the license, and PRs welcome badges. The k8s/arroyo/README documents that directory (a Helm chart for deploying Arroyo on Kubernetes) with installation, quickstart, configuration, and help sections; it does not claim to describe the repository as a whole but is an internal subdirectory README. Both are strong.
What to do
Improve Documentation Quality — currently 8.0/10. — The repository's root README gives a strong overview (what Arroyo is and its main value proposition), links to docs, releases, the license, and PRs welcome badges. The k8s/arroyo/README documents that directory (a Helm chart for deploying Arroyo on Kubernetes) with installation, quickstart, configuration, and help sections; it does not claim to describe the repository as a whole but is an internal subdirectory README. Both are strong.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: 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 ConsistencyStronggated by 2 serious findings◐ 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.
2 API inconsistencies across a 400-member sample of 613 exposed types.
Inconsistent parameter naming for identical signatures. Most connectors use `options` (plural), while ConfluentConnector uses `opts` (abbreviated).
Inconsistent parameter naming for identical signatures. Most connectors use `options` (plural), while ConfluentConnector uses `opts` (abbreviated). Note: ConfluentConnector does not expose `table_from_options`, but the inconsistency in `connection_from_options` is sufficient to flag the naming convention drift.
What to do
Resolve the 1 Inconsistent parameter naming for identical signatures. Most connectors… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Inconsistent parameter naming for identical signatures. Most connectors… 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 any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
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).
45 finding(s): 0 critical, 41 high, 4 medium, 0 low. 31 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 42 file(s) — `crates/arroyo-sql-testing/golden_outputs/async_udf.json`, `crates/arroyo-sql-testing/golden_outputs/cast_to_sink_type.json`, `crates/arroyo-sql-testing/golden_outputs/debezium_agg.json`, `crates/arroyo-sql-testing/golden_outputs/debezium_coercion.json`, `crates/arroyo-sql-testing/golden_outputs/debezium_pass_through.json`, … (+37 more) — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 3 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED (3). — One of this dimension's main actionable groups (6 issue-level).
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
No action in Static Analysis (SAST) — all 31 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 (31 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.
+ 3 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 20 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (14), REDACTED (6). — One of this dimension's main actionable groups (20 issue-level).
Resolve the 2 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 10 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (10). — One of this dimension's main actionable groups (10 warning-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 6 High IaC finding(s) in IaC & Container Security — start with REDACTED (6). — One of this dimension's main actionable groups (6 issue-level).
Resolve the 1 Critical IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 4 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (4). — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
19 of 232 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is crates/arroyo-planner/src/extension/aggregate.rs. Counted over 232 of the 302 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Resolve the 2 Orphaned knowledge finding(s) in Knowledge Freshness — start with aggregate.rs, mod.rs. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 3 Change coupling finding(s) in Change Coupling — start with mod.rs, expiring_time_key_map.rs, table_manager.rs. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
+ 4 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether Kubernetes workloads restrict network EGRESS with a NetworkPolicy (or Cilium policy), limiting where a compromised pod can send data or reach a command-and-control server. Presence of committed egress-restricting policy, not runtime enforcement.
Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn — language-agnostic): Kubernetes workloads gate applicability; credits a NetworkPolicy / Cilium policy that restricts egress (policyTypes: [Egress] / egress rules). Reward-leaning (neutral floor climbing to 10, never a deduction — baseline misconfigs stay with D31). Deterministic.
What it measures: Whether Kubernetes workloads confine the kernel boundary — a seccomp profile (RuntimeDefault/Localhost) plus an AppArmor/SELinux mandatory-access-control layer — shrinking the syscall attack surface a container escape would use. Presence of committed confinement config, not runtime enforcement.
Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn): on Kubernetes workloads, credits a seccomp profile (RuntimeDefault/Localhost) and an AppArmor/SELinux MAC layer. Reward-leaning (neutral floor climbing to 10); NotApplicable without workloads. Deterministic.
Resolve the 1 No seccomp profile finding(s) in Kernel & Syscall Confinement. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 No AppArmor/SELinux confinement finding(s) in Kernel & Syscall Confinement. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d41_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.
No dependency in any ecosystem this repository declares is published as malicious.
✓ On the Gold path — maintain.
Detailed fixes: d43_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives1.0 / 10Critical✓ Tool-verified
Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.
An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. — webui/src/components/WelcomeModal.tsx:30
What to do
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
Do you agree with this assessment?
AC2 · Forms & labels2.9 / 10Weak✓ Tool-verified
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
This UI-library field component has no label / aria-label / aria-labelledby / id / name, and nothing it renders carries one either. The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. (×2) — webui/src/components/ConfigViewer.tsx:59, webui/src/routes/connections/DefineSchema.tsx:475
This UI-library field component has no label / aria-label / aria-labelledby / id / name — and neither does anything it renders — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. (×3) — webui/src/components/StartPipelineModal.tsx:75, webui/src/routes/pipelines/PipelineConfigModal.tsx:69, webui/src/routes/udfs/GlobalizeModal.tsx:125
This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. (×3) — webui/src/routes/connections/DefineSchema.tsx:200, webui/src/routes/connections/DefineSchema.tsx:490, webui/src/routes/connections/DefineSchema.tsx:511
What to do
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it. — webui/index.html:2
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether 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 56 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 your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
What to do
The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
Other · Event Sourcing — Whether the recovery-replay fold is deterministic — state derived purely from each event's own fields, no clock/random/IO on the replay path.
Method: Roslyn syntax scan (event-sourcing gated): Apply/When folds checked for forbidden tokens (DateTime.Now, Guid.NewGuid, Random, IO), stripped of comments/strings. Deterministic, hard fact per fold.
Other · Event Sourcing — Whether domain events stay immutable (private fields, set once) rather than carrying mutable state.
Method: Roslyn scan (event-sourcing gated): persisted events checked for public setters; immutability verified per property/field. Deterministic, hard fact.
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.
129 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
What to do
Add a 'Testing' section to the root README — how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 27 of 27 project(s) that lack one — worth up to 2 pts.
Review the README against recent changes; refresh the parts that drifted.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
Record significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree, with each file named `NNNN-title` in whatever markup those docs already use, is the most discoverable form).
Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
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.
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.
What to do
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
What to do
Add an approval/environment gate (required reviewers / protection rules) before production promotion.
Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.
Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.
No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.
Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.
`reqwest::ClientBuilder::new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. 2 of the 7 files that make outbound calls are unbounded; the first 2 are listed. — crates/arroyo-connectors/src/filesystem/iceberg.rs:37
`Client::new()` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — crates/arroyo-server-common/src/lib.rs:222
What to do
Give every client a whole-request bound: `reqwest::Client::builder().timeout(Duration::from_secs(10))` (never `reqwest::get` or `Client::new()`, which have none), ureq's `timeout_global`, or wrap the call in `tokio::time::timeout`; add retry with back-off (`reqwest-retry`'s `RetryTransientMiddleware`, `backoff`) around dependencies that fail.
Readiness · Readiness — Whether database schema changes go through versioned migrations rather than being auto-created from the model at startup.
Method: Roslyn scan: EF Core DbContext for a versioned migrations directory versus bare EnsureCreated usage; off .NET, a file scan of dependency manifests, migration histories (Flyway, Liquibase, Alembic, Django, Rails, Prisma, TypeORM, Knex/Sequelize, golang-migrate, goose, Laravel, Doctrine, Diesel/sqlx) and schema auto-create in production source or config. Exhaustive, deterministic.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin) or inside a Java method returning a Reactor Mono/Flux — 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.
webui/src/routes/connections/JsonForm.tsx:215 · webui/src/routes/connections/JsonForm.tsx:358 — 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. — webui/src/routes/connections/JsonForm.tsx:215
webui/src/routes/connections/DefineSchema.tsx:212 · webui/src/routes/connections/DefineSchema.tsx:259 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — webui/src/routes/connections/DefineSchema.tsx:212
webui/src/routes/connections/JsonForm.tsx:536 · webui/src/routes/connections/JsonForm.tsx:686 — 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. — webui/src/routes/connections/JsonForm.tsx:536
webui/src/routes/connections/Connections.tsx:202 · webui/src/routes/home/Home.tsx:121 — 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. — webui/src/routes/connections/Connections.tsx:202
webui/src/lib/util.ts:7 · webui/src/lib/util.ts:32 · webui/src/lib/util.ts:57 — all 3 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. — webui/src/lib/util.ts:7
webui/src/routes/connections/JsonForm.tsx:497 · webui/src/routes/connections/JsonForm.tsx:661 — 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. — webui/src/routes/connections/JsonForm.tsx:497
webui/src/routes/connections/ConnectionTester.tsx:205 · webui/src/routes/connections/CreateProfile.tsx:134 — 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. — webui/src/routes/connections/ConnectionTester.tsx:205
webui/src/routes/connections/CreateConnection.tsx:49 · webui/src/routes/connections/CreateConnection.tsx:81 — 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. — webui/src/routes/connections/CreateConnection.tsx:49
webui/src/routes/not_found/ApiUnavailable.tsx:5 · webui/src/routes/not_found/PageNotFound.tsx:5 — 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. — webui/src/routes/not_found/ApiUnavailable.tsx:5
webui/src/routes/udfs/UdfsResourceTab.tsx:69 · webui/src/routes/udfs/UdfsResourceTab.tsx:102 — 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. — webui/src/routes/udfs/UdfsResourceTab.tsx:69
webui/src/lib/data_fetching.ts:511 · webui/src/lib/data_fetching.ts:591 — 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. — webui/src/lib/data_fetching.ts:511
webui/src/components/PipelinesTable.tsx:40 · webui/src/routes/connections/Connections.tsx:108 — the two spans are one implementation copied and then locally edited — 75 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. — webui/src/components/PipelinesTable.tsx:40
webui/src/routes/connections/DefineSchema.tsx:443 · webui/src/routes/connections/DefineSchema.tsx:455 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — webui/src/routes/connections/DefineSchema.tsx:443
webui/src/routes/connections/JsonForm.tsx:525 · webui/src/routes/connections/JsonForm.tsx:647 — all 2 copies are in the same file, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — webui/src/routes/connections/JsonForm.tsx:525
webui/src/components/CreatePipelineTourModal.tsx:24 · webui/src/components/TourCompleteModal.tsx:25 — 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. — webui/src/components/CreatePipelineTourModal.tsx:24
webui/src/routes/connections/JsonForm.tsx:865 · webui/src/routes/connections/JsonForm.tsx:914 — 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. — webui/src/routes/connections/JsonForm.tsx:865
webui/src/components/CheckpointDetails.tsx:78 · webui/src/components/CheckpointDetails.tsx:128 — 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. — webui/src/components/CheckpointDetails.tsx:78
webui/src/components/PipelinesTable.tsx:45 · webui/src/components/PipelinesTable.tsx:55 — the two spans are one implementation copied and then locally edited — 59 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — webui/src/components/PipelinesTable.tsx:45
webui/src/components/CheckpointDetails.tsx:42 · webui/src/components/PipelineRow.tsx:67 — 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. — webui/src/components/CheckpointDetails.tsx:42
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · Architecture — Conformance to the detected frontend architecture layout (feature-sliced / layered src) plus cross-package deep-import rules (D-386).
Method: Conformance to the detected frontend layout (feature-sliced / layered src) plus cross-package deep-import rules, over the module graph. Deterministic.
webui/src/components/ExampleQueryCard.tsx:18 imports react-syntax-highlighter/dist/esm/styles/hljs, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — webui/src/components/ExampleQueryCard.tsx:18
webui/src/routes/connections/JsonForm.tsx:27 imports ajv/dist/2019, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — webui/src/routes/connections/JsonForm.tsx:27
webui/src/routes/pipelines/CreatePipeline.tsx:52 imports react-syntax-highlighter/dist/esm/styles/hljs, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — webui/src/routes/pipelines/CreatePipeline.tsx:52
webui/src/routes/pipelines/PipelineDetails.tsx:66 imports react-syntax-highlighter/dist/esm/styles/hljs, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — webui/src/routes/pipelines/PipelineDetails.tsx:66
webui/src/routes/udfs/UdfNodePopover.tsx:20 imports react-syntax-highlighter/dist/esm/styles/hljs, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — webui/src/routes/udfs/UdfNodePopover.tsx:20
What to do
Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
CreatePipeline has cyclomatic complexity 38 and cognitive complexity 44; 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. — webui/src/routes/pipelines/CreatePipeline.tsx:75
(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. — webui/src/routes/connections/JsonForm.tsx:751
PipelineDetails has cyclomatic complexity 25 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — webui/src/routes/pipelines/PipelineDetails.tsx:69
Checkpoints has cyclomatic complexity 24 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — webui/src/components/Checkpoints.tsx:91
ConnectionTester has cyclomatic complexity 22 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. — webui/src/routes/connections/ConnectionTester.tsx:36
SchemaFormatEditor 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. — webui/src/routes/connections/DefineSchema.tsx:25
(anonymous) has cyclomatic complexity 16 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — webui/src/components/CheckpointDetails.tsx:58
ConfigEntry has cyclomatic complexity 13 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 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. — webui/src/components/ConfigViewer.tsx:105
AutocompleteWidget has cyclomatic complexity 12 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — webui/src/routes/connections/JsonForm.tsx:230
What to do
Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
Do you agree with this assessment?
R3 · Large Files7.5 / 10Strong✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
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?
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.3 / 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 1 application, 2 tooling and 0 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
no import path from any entry point (1 application, 2 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×2) — webui/src/lib/RadioGroup.tsx, webui/src/routes/pipelines/ResourcePanel.tsx
Nothing imports this binding — it is safe to review for removal. (×3) — webui/src/lib/util.ts:3, webui/src/lib/util.ts:29, webui/src/lib/util.ts:79
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 webui/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.
webui/src/App.tsx → webui/src/lib/CloudComponents.tsx → webui/src/router.tsx → webui/src/App.tsx (one verified cycle inside a mutually-dependent group of 10 files) — webui/src/App.tsx
What to do
Break each cycle by extracting the shared piece into a module both sides can import.
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.
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 13 of 55 WCAG 2.2 Level A/AA success criteria (24%; ≈26% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 42 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 — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X6 Hand-rolled structured-format parsing — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 65 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.
AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
AX1 Captive dependencies — Not applicable: this repository's Python imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — docker build failed (exit 1) — DEPRECATED: The legacy builder is deprecated and will be removed in a future release.
Install the buildx component to build images with BuildKit:
https://docs.docker.com/go/bui…; 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.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
D10 Test Quality — ~2026 lines of test source are present (.rs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
D11 Test Reliability — Test reliability not included — the .rs suite was found but not re-run
D14 License Compliance — Not scored — this repository's 910 shipped crate(s) were read from its REDACTED, but crates.io could not be asked for the licence of 32 of them (HTTP 429 Unknown Error), and a licence verdict over part of a dependency graph is not a licence verdict. Nothing is asserted about this repository's licensing in either direction.
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. 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.
D25 ADR Conformance — no ADRs to check
D27 Navigability — symbol resolution incomplete — navigability not assessed
D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
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.
D42 Runtime Threat Enforcement — The repository ships application workloads but no cluster-governance resources (CRDs, admission webhooks, or a committed policy engine). Runtime threat-detection (Falco/Tetragon) and admission control (Kyverno/OPA-Gatekeeper/PodSecurity) are cluster-OPERATOR controls owned by the platform, not shipped by an application repo/chart — nothing for this repo to assess.
D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not included — suite not readable by the collector
DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 48 value object(s); 1 domain event(s); its domain events are published by services or handlers — no domain entity raises one
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
ED5 Idempotency — This check finds retry-prone mutations (command handlers and message/event consumers) by walking the repository's declared types, and none was loaded here, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
GD1 Unfinished & placeholder code — no source files were read — this check reads C# syntax, and none was loaded for this repository. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `#[bench]`, criterion's `bench_function`/`bench_with_input`, `#[divan::bench]` or `#[library_benchmark]` in any `.rs` file, or criterion, divan, iai or a `[[bench]]` target in a Cargo.toml, 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: Rust spells out every heap allocation and makes borrowed slices (&[T], &str) its ordinary parameter types, so the allocation-aware style this card rewards elsewhere is the language's baseline rather than a rung to climb. 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.
R4 Test Coverage — the JS/TS workspace (62 production file(s)) has no JavaScript/TypeScript test, but it is 10.76% of this repository's production source and the other 89.24% carries 2,026 line(s) of test code this pass cannot read — an incidental frontend's reachability is not the repository's test posture, so it is not scored as one
R5 Dependency Freshness — uses a pnpm lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
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.
X1 Async correctness — 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
X12 Unreachable branch — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X13 Undrained process stream — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X14 Bypassable address classification — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X15 Unvalidated length from an untrusted reader — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X16 Unfloored truncation loop — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X17 Uncapped recursion over a caller-supplied document — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X18 Disposal-pattern correctness — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X19 Unrestored process-global state — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X2 Cancellation propagation — 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
X20 Mistyped argument guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X21 Side-effecting pattern guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X22 Contradicted release guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X23 Unguarded diagnostic materialisation — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X24 Document value interpolated into markup unescaped — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X25 Inert configuration knob — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X26 Unsynchronised callback handoff — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X27 Collection changed while being enumerated — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X28 Index access outside its own emptiness guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X3 Exception handling — 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
X30 Support guard that admits what it rejects — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X5 Nullable reference types — 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
X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
Orphaned knowledge crates/arroyo-planner/src/extension/aggregate.rs— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge crates/arroyo-connectors/src/nats/source/mod.rs— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
AC1 · Text alternatives· <img> without a text alternative · ×1
<img> without a text alternative webui/src/components/WelcomeModal.tsx:30— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
TodoComment crates/arroyo-api/src/pipelines.rs:144— // TODO: Allow pipeline requests to select explicit connection versions. For now, — 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 crates/arroyo-api/src/pipelines.rs:480— // TODO: program features — 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 crates/arroyo-api/src/lib.rs:124— // TODO: cache this — 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 crates/arroyo-api/src/jobs.rs:155— // TODO: handle chance of collision in ids — 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 crates/arroyo-api/src/jobs.rs:225— // TODO: Note that this is not transactional, as we don't have the ability to do transactions in — 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 crates/arroyo-api/src/jobs.rs:546— // TODO: make this check more robust — 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 crates/arroyo-api/src/connection_tables.rs:988— // TODO: add testing for other schema types — 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 crates/arroyo-connectors/src/filesystem/source.rs:98— // TODO: sort by creation time — 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 crates/arroyo-connectors/src/filesystem/mod.rs:90— // TODO: support local paths for iceberg — 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 crates/arroyo-connectors/src/filesystem/sink/two_phase_committer.rs:51— // TODO: figure out how to have the relevant vectors be of pointers across async boundaries. — 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 crates/arroyo-connectors/src/filesystem/sink/parquet.rs:212— // TODO: this copy can likely be avoided, as the section we are copying is immutable — 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 crates/arroyo-connectors/src/filesystem/sink/mod.rs:472— // TODO: this recovery code duplicates some complex and important logic from — 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 crates/arroyo-connectors/src/filesystem/sink/mod.rs:1277— // TODO: use Bytes to avoid clone — 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 crates/arroyo-connectors/src/filesystem/sink/local.rs:57— // TODO: explore configuration options here — 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 crates/arroyo-connectors/src/filesystem/sink/local.rs:364— // TODO: this breaks iceberg, but we don't support iceberg on local filesystem anyways — 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 crates/arroyo-connectors/src/filesystem/sink/v2/open_file.rs:460— // TODO: plug in to a global max in flight parts limit — 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 crates/arroyo-connectors/src/filesystem/sink/v2/open_file.rs:467— // TODO: it's possible that we could start multiple uploads at this point and get — 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 crates/arroyo-connectors/src/filesystem/sink/v2/open_file.rs:800— // TODO: handle the (implausible but possible) case that the single file is larger — 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 crates/arroyo-connectors/src/kafka/sink/test.rs:52— // TODO: parameterize group id — 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 crates/arroyo-connectors/src/kafka/sink/test.rs:115— // TODO: parameterize group id — 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 crates/arroyo-connectors/src/kafka/source/test.rs:55— // TODO: parameterize group id — 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 crates/arroyo-connectors/src/kafka/source/test.rs:176— // TODO: parameterize group id — 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 crates/arroyo-connectors/src/kafka/sink/mod.rs:311— // TODO: this copy should be unnecessary but likely needs a custom trait impl — 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 crates/arroyo-connectors/src/kinesis/source.rs:285— // TODO: make retry behavior configurable — 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 crates/arroyo-connectors/src/nats/mod.rs:203— // TODO: Implement a full-fledge `NatsTester` struct for testing the client connection, — 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.
FileTooLong: sink/mod.rs crates/arroyo-connectors/src/filesystem/sink/mod.rs— FileTooLong — 1478 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 978 over it, 2.96× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/lib.rs crates/arroyo-worker/src/lib.rs— FileTooLong — 1051 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 551 over it, 2.10× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/operator.rs crates/arroyo-operator/src/operator.rs— FileTooLong — 1049 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 549 over it, 2.10× 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: connections/JsonForm.tsx webui/src/routes/connections/JsonForm.tsx— FileTooLong — 891 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 391 over it, 1.78× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: tables/expiring_time_key_map.rs crates/arroyo-state/src/tables/expiring_time_key_map.rs— FileTooLong — 882 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 382 over it, 1.76× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/lib.rs crates/arroyo-rpc/src/lib.rs— FileTooLong — 867 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 367 over it, 1.73× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/physical.rs crates/arroyo-planner/src/physical.rs— FileTooLong — 861 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 361 over it, 1.72× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/pipelines.rs crates/arroyo-api/src/pipelines.rs— FileTooLong — 843 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 343 over it, 1.69× 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 — 823 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 67% of them inside a single declaration: IncrementalAggregatingFunc (3 blocks, 200-1024). The bar is 500 significant lines; this is 323 over it, 1.65× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/lib.rs crates/arroyo-planner/src/lib.rs— FileTooLong — 806 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 306 over it, 1.61× 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: v2/open_file.rs crates/arroyo-connectors/src/filesystem/sink/v2/open_file.rs— FileTooLong — 799 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 81% of them inside a single declaration: OpenFile (2 blocks, 205-1104). The bar is 500 significant lines; this is 299 over it, 1.60× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/tables.rs crates/arroyo-planner/src/tables.rs— FileTooLong — 751 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 251 over it, 1.50× 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: kafka/mod.rs crates/arroyo-connectors/src/kafka/mod.rs— FileTooLong — 736 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 236 over it, 1.47× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: states/mod.rs crates/arroyo-controller/src/states/mod.rs— FileTooLong — 718 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 218 over it, 1.44× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/connection_tables.rs crates/arroyo-api/src/connection_tables.rs— FileTooLong — 707 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 207 over it, 1.41× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: nexmark/operator.rs crates/arroyo-connectors/src/nexmark/operator.rs— FileTooLong — 699 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 199 over it, 1.40× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/engine.rs crates/arroyo-worker/src/engine.rs— FileTooLong — 692 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 192 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: arrow/session_aggregating_window.rs crates/arroyo-worker/src/arrow/session_aggregating_window.rs— FileTooLong — 682 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 182 over it, 1.36× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/lib.rs crates/arroyo-storage/src/lib.rs— FileTooLong — 681 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 60% of them inside a single declaration: StorageProvider (3 blocks, 56-1026). The bar is 500 significant lines; this is 181 over it, 1.36× 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: v2/mod.rs crates/arroyo-connectors/src/filesystem/sink/v2/mod.rs— FileTooLong — 675 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 65% of them inside a single declaration: FileSystemSinkV2 (3 blocks, 256-957). The bar is 500 significant lines; this is 175 over it, 1.35× 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: filesystem/config.rs crates/arroyo-connectors/src/filesystem/config.rs— FileTooLong — 659 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 159 over it, 1.32× 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: schedulers/mod.rs crates/arroyo-controller/src/schedulers/mod.rs— FileTooLong — 631 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 131 over it, 1.26× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/config.rs crates/arroyo-rpc/src/config.rs— FileTooLong — 619 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 119 over it, 1.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: job_controller/controller.rs crates/arroyo-worker/src/job_controller/controller.rs— FileTooLong — 594 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 87% of them inside a single declaration: WorkerJobController (3 blocks, 45-867). The bar is 500 significant lines; this is 94 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: src/workflow.rs crates/arroyo-state-protocol/src/workflow.rs— FileTooLong — 587 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). 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.
MethodTooLong: Scheduling.next crates/arroyo-controller/src/states/scheduling.rs:369— MethodTooLong — next runs 246 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 146 over it, 2.46× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: LeaderRunning.next crates/arroyo-controller/src/states/leader_running.rs:29— MethodTooLong — next runs 148 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 48 over it, 1.48× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ConnectorTable.from_options crates/arroyo-planner/src/tables.rs:235— MethodTooLong — from_options runs 146 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 46 over it, 1.46× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: RunningJobModel.finish_checkpoint crates/arroyo-worker/src/job_controller/model.rs:354— MethodTooLong — finish_checkpoint runs 145 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 45 over it, 1.45× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: WorkerJobController.init crates/arroyo-worker/src/job_controller/controller.rs:85— MethodTooLong — init runs 142 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 42 over it, 1.42× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: NatsSourceFunc.run_int crates/arroyo-connectors/src/nats/source/mod.rs:323— MethodTooLong — run_int runs 138 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 38 over it, 1.38× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: WorkerJobController.start_inner crates/arroyo-worker/src/job_controller/controller.rs:292— MethodTooLong — start_inner runs 136 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 36 over it, 1.36× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: WorkerState.run_control_loop crates/arroyo-worker/src/lib.rs:467— MethodTooLong — run_control_loop runs 133 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 33 over it, 1.33× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AggregateRewriter.f_up crates/arroyo-planner/src/plan/aggregate.rs:124— MethodTooLong — f_up runs 129 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 29 over it, 1.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.
MethodTooLong: Program.from_logical crates/arroyo-worker/src/engine.rs:210— MethodTooLong — from_logical runs 124 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: IncrementalAggregatingFunc.initialize REDACTED:446— MethodTooLong — initialize runs 120 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 20 over it, 1.20× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: WindowDetectingVisitor.f_up crates/arroyo-planner/src/plan/mod.rs:93— MethodTooLong — f_up runs 116 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 16 over it, 1.16× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: IncrementalAggregatingConstructor.with_config REDACTED:1038— MethodTooLong — with_config runs 116 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 16 over it, 1.16× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ArroyoRewriter.f_up crates/arroyo-planner/src/plan/mod.rs:264— MethodTooLong — f_up runs 115 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 15 over it, 1.15× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: RedisConnector.from_options crates/arroyo-connectors/src/redis/mod.rs:232— MethodTooLong — from_options runs 112 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 12 over it, 1.12× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: KafkaTester.validate_schema crates/arroyo-connectors/src/kafka/mod.rs:598— MethodTooLong — validate_schema runs 111 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 11 over it, 1.11× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: RunningJobModel.handle_message crates/arroyo-worker/src/job_controller/model.rs:143— MethodTooLong — handle_message runs 111 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 11 over it, 1.11× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: CheckpointState.checkpoint_finished crates/arroyo-worker/src/job_controller/checkpoint_state.rs:271— MethodTooLong — checkpoint_finished runs 110 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 10 over it, 1.10× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AsyncUdfOperator.on_start crates/arroyo-worker/src/arrow/async_udf.rs:155— MethodTooLong — on_start runs 109 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) 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.
MethodTooLong: ImpulseSourceFunc.run crates/arroyo-connectors/src/impulse/operator.rs:96— MethodTooLong — run runs 108 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 8 over it, 1.08× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: NatsSourceFunc.create_nats_consumer crates/arroyo-connectors/src/nats/source/mod.rs:162— MethodTooLong — create_nats_consumer runs 106 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) 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.
MethodTooLong: Table.try_from_statement crates/arroyo-planner/src/tables.rs:772— MethodTooLong — try_from_statement runs 106 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) 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.
MethodTooLong: WorkerState.initialize_inner crates/arroyo-worker/src/lib.rs:322— MethodTooLong — initialize_inner runs 105 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 5 over it, 1.05× 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: CreatePipeline.CreatePipeline webui/src/routes/pipelines/CreatePipeline.tsx:75— FunctionTooLong — CreatePipeline runs 504 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 404 over it, 5.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: PipelineDetails.PipelineDetails webui/src/routes/pipelines/PipelineDetails.tsx:69— FunctionTooLong — PipelineDetails runs 295 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 195 over it, 2.95× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: JsonForm.FormInner webui/src/routes/connections/JsonForm.tsx:703— FunctionTooLong — FormInner runs 216 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 116 over it, 2.16× 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: CheckpointDetails.CheckpointTimeline webui/src/components/CheckpointDetails.tsx:54— FunctionTooLong — CheckpointTimeline runs 204 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 104 over it, 2.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: ConnectionTester.ConnectionTester webui/src/routes/connections/ConnectionTester.tsx:36— FunctionTooLong — ConnectionTester runs 151 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 51 over it, 1.51× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: SchemaEditor.SchemaEditor webui/src/routes/connections/SchemaEditor.tsx:21— FunctionTooLong — SchemaEditor runs 148 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 48 over it, 1.48× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: arroyo_formats::avro::ser::serialize_column crates/arroyo-formats/src/avro/ser.rs:63— FunctionTooLong — arroyo_formats::avro::ser::serialize_column runs 144 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 44 over it, 1.44× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: arroyo_api::pipelines::create_pipeline_int crates/arroyo-api/src/pipelines.rs:300— FunctionTooLong — arroyo_api::pipelines::create_pipeline_int runs 143 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 43 over it, 1.43× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: Connections.Connections webui/src/routes/connections/Connections.tsx:71— FunctionTooLong — Connections runs 141 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 41 over it, 1.41× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: PipelineConfigs.PipelineConfigs webui/src/routes/pipelines/PipelineConfigs.tsx:113— FunctionTooLong — PipelineConfigs runs 134 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 34 over it, 1.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: PipelineOutputs.PipelineOutputs webui/src/routes/pipelines/PipelineOutputs.tsx:9— FunctionTooLong — PipelineOutputs runs 132 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 32 over it, 1.32× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: JsonForm.AutocompleteWidget webui/src/routes/connections/JsonForm.tsx:230— FunctionTooLong — AutocompleteWidget runs 124 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: arroyo_controller::states::execute_state crates/arroyo-controller/src/states/mod.rs:579— FunctionTooLong — arroyo_controller::states::execute_state runs 118 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 18 over it, 1.18× 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: JsonForm.MapWidget webui/src/routes/connections/JsonForm.tsx:553— FunctionTooLong — MapWidget runs 116 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 16 over it, 1.16× 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: arroyo_planner::parse_and_get_arrow_program crates/arroyo-planner/src/lib.rs:834— FunctionTooLong — arroyo_planner::parse_and_get_arrow_program runs 106 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) 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: GlobalizeModal.GlobalizeModal webui/src/routes/udfs/GlobalizeModal.tsx:34— FunctionTooLong — GlobalizeModal runs 105 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 5 over it, 1.05× 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: PipelinesTable.PipelinesTable webui/src/components/PipelinesTable.tsx:29— FunctionTooLong — PipelinesTable runs 104 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 4 over it, 1.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: arroyo_connectors::filesystem::sink::from_checkpoint crates/arroyo-connectors/src/filesystem/sink/mod.rs:465— FunctionTooLong — arroyo_connectors::filesystem::sink::from_checkpoint runs 103 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 3 over it, 1.03× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D30 · Dependency Vulnerabilities· Medium vulnerability · ×10
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
D30 · Dependency Vulnerabilities· Medium advisory (unmaintained) · ×9
Duplicated block (7 lines × 2) crates/arroyo-connectors/src/filesystem/sink/v2/open_file.rs:711— crates/arroyo-connectors/src/filesystem/sink/v2/open_file.rs:711-717 | crates/arroyo-connectors/src/filesystem/sink/v2/open_file.rs:719-725 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) crates/arroyo-connectors/src/fluvio/sink.rs:82— crates/arroyo-connectors/src/fluvio/sink.rs:82-88 | crates/arroyo-connectors/src/fluvio/source.rs:75-81 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) crates/arroyo-controller/src/states/scheduling.rs:644— crates/arroyo-controller/src/states/scheduling.rs:644-650 | crates/arroyo-controller/src/states/scheduling.rs:686-693 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) crates/arroyo-planner/src/plan/mod.rs:118— crates/arroyo-planner/src/plan/mod.rs:118-124 | crates/arroyo-planner/src/plan/mod.rs:190-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 (7 lines × 2) crates/arroyo-state/src/tables/expiring_time_key_map.rs:269— crates/arroyo-state/src/tables/expiring_time_key_map.rs:269-276 | crates/arroyo-state/src/tables/expiring_time_key_map.rs:421-427 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) crates/arroyo-worker/src/engine.rs:399— crates/arroyo-worker/src/engine.rs:399-405 | crates/arroyo-worker/src/engine.rs:415-421 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) crates/arroyo-connectors/src/rabbitmq/mod.rs:99— crates/arroyo-connectors/src/rabbitmq/mod.rs:99-105 | crates/arroyo-connectors/src/redis/mod.rs:239-245 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) crates/arroyo-planner/src/physical.rs:902— crates/arroyo-planner/src/physical.rs:902-908 | crates/arroyo-planner/src/physical.rs:910-916 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) crates/arroyo-connectors/src/polling_http/mod.rs:130— crates/arroyo-connectors/src/polling_http/mod.rs:130-136 | crates/arroyo-connectors/src/webhook/mod.rs:115-121 — `crates/arroyo-connectors/src/polling_http/mod.rs` and `crates/arroyo-connectors/src/webhook/mod.rs` 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 4 separate duplicated blocks between them, totalling at least 35 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.
ClassTooLong: OpenFile crates/arroyo-connectors/src/filesystem/sink/v2/open_file.rs:205— ClassTooLong — 651 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 19 methods, 2 blocks, lines 205-1104. The bar is 400 significant lines; this is 251 over it, 1.63× 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: IncrementalAggregatingFunc REDACTED:200— ClassTooLong — 554 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 14 methods, 3 blocks, lines 200-1024. The bar is 400 significant lines; this is 154 over it, 1.39× 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: WorkerJobController crates/arroyo-worker/src/job_controller/controller.rs:45— ClassTooLong — 517 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 17 methods, 3 blocks, lines 45-867. The bar is 400 significant lines; this is 117 over it, 1.29× 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: CreatePipeline webui/src/routes/pipelines/CreatePipeline.tsx:1— ClassTooLong — 504 significant lines (blank, comment-only and punctuation-only lines excluded), 2 methods. The bar is 400 significant lines; this is 104 over it, 1.26× 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: RunningJobModel crates/arroyo-worker/src/job_controller/model.rs:37— ClassTooLong — 471 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 14 methods, 3 blocks, lines 37-702. The bar is 400 significant lines; this is 71 over it, 1.18× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: FileSystemSinkV2 crates/arroyo-connectors/src/filesystem/sink/v2/mod.rs:256— ClassTooLong — 437 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 7 methods, 3 blocks, lines 256-957. The bar is 400 significant lines; this is 37 over it, 1.09× 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: StorageProvider crates/arroyo-storage/src/lib.rs:56— ClassTooLong — 408 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 34 methods, 3 blocks, lines 56-1026. The bar is 400 significant lines; this is 8 over it, 1.02× 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.
Off the main sequence: arroyo-udf-common — arroyo-udf-common: abstractness 0.00, instability 0.00, distance 1.00 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.
Off the main sequence: arroyo-rpc — arroyo-rpc: abstractness 0.03, instability 0.06, distance 0.91 — zone of pain — concrete and depended on by 16 project(s), so it's rigid to change.
Off the main sequence: arroyo-udf-host — arroyo-udf-host: abstractness 0.00, instability 0.17, distance 0.83 — zone of pain — concrete and depended on by 5 project(s), so it's rigid to change.
Off the main sequence: arroyo-types — arroyo-types: abstractness 0.19, instability 0.00, distance 0.81 — zone of pain — concrete and depended on by 16 project(s), so it's rigid to change.
Off the main sequence: arroyo-udf-python — arroyo-udf-python: abstractness 0.00, instability 0.20, distance 0.80 — zone of pain — concrete and depended on by 4 project(s), so it's rigid to change.
Off the main sequence: arroyo-datastream — arroyo-datastream: abstractness 0.06, instability 0.17, distance 0.77 — zone of pain — concrete and depended on by 5 project(s), so it's rigid to change.
Off the main sequence: arroyo-storage — arroyo-storage: abstractness 0.00, instability 0.25, distance 0.75 — zone of pain — concrete and depended on by 6 project(s), so it's rigid to change.
Duplicated block (13 lines × 2) crates/arroyo-connectors/src/filesystem/sink/json.rs:319— crates/arroyo-connectors/src/filesystem/sink/json.rs:319-331 | crates/arroyo-connectors/src/filesystem/sink/parquet.rs:294-306 — 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) crates/arroyo-connectors/src/redis/mod.rs:119— crates/arroyo-connectors/src/redis/mod.rs:119-131 | crates/arroyo-connectors/src/redis/mod.rs:135-147 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) REDACTED:453— REDACTED:453-465 | REDACTED:509-521 — 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) crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs:604— crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs:604-616 | crates/arroyo-worker/src/arrow/tumbling_aggregating_window.rs:256-268 — before extracting anything, compare `crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs` and `crates/arroyo-worker/src/arrow/tumbling_aggregating_window.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 105 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs:699— crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs:699-711 | crates/arroyo-worker/src/arrow/tumbling_aggregating_window.rs:436-448 — before extracting anything, compare `crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs` and `crates/arroyo-worker/src/arrow/tumbling_aggregating_window.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 105 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) crates/arroyo-controller/src/leader_manager.rs:221— crates/arroyo-controller/src/leader_manager.rs:221-233 | crates/arroyo-controller/src/states/leader_restarting.rs:66-78 — 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.
AC2 · Forms & labels· <Select> field component without a label · ×5
<Select> field component without a label webui/src/components/ConfigViewer.tsx:59— This UI-library field component has no label / aria-label / aria-labelledby / id / name, and nothing it renders carries one either. The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Select> field component without a label webui/src/routes/connections/DefineSchema.tsx:200— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Select> field component without a label webui/src/routes/connections/DefineSchema.tsx:475— This UI-library field component has no label / aria-label / aria-labelledby / id / name, and nothing it renders carries one either. The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Select> field component without a label webui/src/routes/connections/DefineSchema.tsx:490— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Select> field component without a label webui/src/routes/connections/DefineSchema.tsx:511— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
Hotspot: crates/arroyo-controller/src/states/scheduling.rs crates/arroyo-controller/src/states/scheduling.rs:369— crates/arroyo-controller/src/states/scheduling.rs changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in Scheduling::next at line 369. 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-06-27..2026-09-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-27 09:29:23 -07:00' --until='2026-09-25 09:29:23 -07:00' --full-history --no-merges -- crates/arroyo-controller/src/states/scheduling.rs`: 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: crates/arroyo-controller/src/states/leader_running.rs crates/arroyo-controller/src/states/leader_running.rs:29— crates/arroyo-controller/src/states/leader_running.rs changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in LeaderRunning::next at line 29. 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-06-27..2026-09-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-27 09:29:23 -07:00' --until='2026-09-25 09:29:23 -07:00' --full-history --no-merges -- crates/arroyo-controller/src/states/leader_running.rs`: 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: crates/arroyo-worker/src/job_controller/controller.rs crates/arroyo-worker/src/job_controller/controller.rs:292— crates/arroyo-worker/src/job_controller/controller.rs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in WorkerJobController::start_inner at line 292. 1 of those changes was a fix/bug commit, and the other 4 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-06-27..2026-09-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-27 09:29:23 -07:00' --until='2026-09-25 09:29:23 -07:00' --full-history --no-merges -- crates/arroyo-worker/src/job_controller/controller.rs`: 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: crates/arroyo-controller/src/states/mod.rs crates/arroyo-controller/src/states/mod.rs:892— crates/arroyo-controller/src/states/mod.rs changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in StateMachine::start at line 892. 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-06-27..2026-09-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-27 09:29:23 -07:00' --until='2026-09-25 09:29:23 -07:00' --full-history --no-merges -- crates/arroyo-controller/src/states/mod.rs`: 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: webui/src/routes/pipelines/PipelineDetails.tsx webui/src/routes/pipelines/PipelineDetails.tsx:69— webui/src/routes/pipelines/PipelineDetails.tsx changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in PipelineDetails.PipelineDetails at line 69. 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-06-27..2026-09-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-27 09:29:23 -07:00' --until='2026-09-25 09:29:23 -07:00' --full-history --no-merges -- webui/src/routes/pipelines/PipelineDetails.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.
D30 · Dependency Vulnerabilities· Medium advisory (unsound) · ×5
Duplicated block (9 lines × 2) crates/arroyo-connectors/src/fluvio/source.rs:186— crates/arroyo-connectors/src/fluvio/source.rs:186-194 | crates/arroyo-connectors/src/kafka/source/mod.rs:239-247 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 2) crates/arroyo-state/src/tables/global_keyed_map.rs:102— crates/arroyo-state/src/tables/global_keyed_map.rs:102-110 | crates/arroyo-state/src/tables/global_keyed_map.rs:168-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 (9 lines × 2) crates/arroyo-udf/arroyo-udf-python/src/pyarrow.rs:183— crates/arroyo-udf/arroyo-udf-python/src/pyarrow.rs:183-191 | crates/arroyo-udf/arroyo-udf-python/src/pyarrow.rs:208-216 — 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) crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs:275— crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs:275-283 | crates/arroyo-worker/src/arrow/tumbling_aggregating_window.rs:65-73 — before extracting anything, compare `crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs` and `crates/arroyo-worker/src/arrow/tumbling_aggregating_window.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 105 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) crates/arroyo-worker/src/job_controller/model.rs:150— crates/arroyo-worker/src/job_controller/model.rs:150-158 | crates/arroyo-worker/src/job_controller/model.rs:184-192 — 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.
Boundary violation [package:third-party-deep-import] webui/src/components/ExampleQueryCard.tsx:18— webui/src/components/ExampleQueryCard.tsx:18 imports react-syntax-highlighter/dist/esm/styles/hljs, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] webui/src/routes/connections/JsonForm.tsx:27— webui/src/routes/connections/JsonForm.tsx:27 imports ajv/dist/2019, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] webui/src/routes/pipelines/CreatePipeline.tsx:52— webui/src/routes/pipelines/CreatePipeline.tsx:52 imports react-syntax-highlighter/dist/esm/styles/hljs, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] webui/src/routes/pipelines/PipelineDetails.tsx:66— webui/src/routes/pipelines/PipelineDetails.tsx:66 imports react-syntax-highlighter/dist/esm/styles/hljs, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] webui/src/routes/udfs/UdfNodePopover.tsx:20— webui/src/routes/udfs/UdfNodePopover.tsx:20 imports react-syntax-highlighter/dist/esm/styles/hljs, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Duplicated block (16 lines × 2) crates/arroyo-connectors/src/filesystem/source.rs:319— crates/arroyo-connectors/src/filesystem/source.rs:319-334 | crates/arroyo-connectors/src/filesystem/source.rs:358-373 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) crates/arroyo-connectors/src/kafka/mod.rs:680— crates/arroyo-connectors/src/kafka/mod.rs:680-695 | crates/arroyo-connectors/src/kafka/mod.rs:723-738 — 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) crates/arroyo-connectors/src/sse/mod.rs:106— crates/arroyo-connectors/src/sse/mod.rs:106-121 | crates/arroyo-connectors/src/websocket/mod.rs:248-263 — `crates/arroyo-connectors/src/sse/mod.rs` and `crates/arroyo-connectors/src/websocket/mod.rs` 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 5 separate duplicated blocks between them, totalling at least 54 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.
Duplicated block (16 lines × 2) crates/arroyo-state/src/tables/table_manager.rs:437— crates/arroyo-state/src/tables/table_manager.rs:437-452 | crates/arroyo-state/src/tables/table_manager.rs:478-493 — 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) crates/arroyo-api/src/connection_tables.rs:239— crates/arroyo-api/src/connection_tables.rs:239-248 | crates/arroyo-api/src/connection_tables.rs:548-557 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) crates/arroyo-connectors/src/filesystem/config.rs:464— crates/arroyo-connectors/src/filesystem/config.rs:464-473 | crates/arroyo-connectors/src/filesystem/config.rs:541-550 — 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) crates/arroyo-worker/src/engine.rs:334— crates/arroyo-worker/src/engine.rs:334-343 | crates/arroyo-worker/src/engine.rs:352-361 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) crates/arroyo-planner/src/builder.rs:359— crates/arroyo-planner/src/builder.rs:359-368 | crates/arroyo-planner/src/builder.rs:386-396 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) crates/arroyo-connectors/src/filesystem/sink/iceberg/transforms.rs:156— crates/arroyo-connectors/src/filesystem/sink/iceberg/transforms.rs:156-163 | crates/arroyo-connectors/src/filesystem/sink/iceberg/transforms.rs:180-187 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) crates/arroyo-worker/src/arrow/join_with_expiration.rs:56— crates/arroyo-worker/src/arrow/join_with_expiration.rs:56-63 | crates/arroyo-worker/src/arrow/join_with_expiration.rs:91-98 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs:649— crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs:649-656 | crates/arroyo-worker/src/arrow/tumbling_aggregating_window.rs:294-301 — before extracting anything, compare `crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs` and `crates/arroyo-worker/src/arrow/tumbling_aggregating_window.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 105 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) crates/arroyo-connectors/src/fluvio/mod.rs:92— crates/arroyo-connectors/src/fluvio/mod.rs:92-99 | crates/arroyo-connectors/src/rabbitmq/mod.rs:142-149 — `crates/arroyo-connectors/src/fluvio/mod.rs` and `crates/arroyo-connectors/src/rabbitmq/mod.rs` 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 7 separate duplicated blocks between them, totalling at least 67 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.
Duplicated block (6 lines × 2) crates/arroyo-connectors/src/filesystem/sink/iceberg/schema.rs:54— crates/arroyo-connectors/src/filesystem/sink/iceberg/schema.rs:54-59 | crates/arroyo-connectors/src/filesystem/sink/iceberg/schema.rs:153-158 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) crates/arroyo-operator/src/context.rs:521— crates/arroyo-operator/src/context.rs:521-526 | crates/arroyo-state/src/tables/expiring_time_key_map.rs:560-567 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) crates/arroyo-planner/src/extension/aggregate.rs:508— crates/arroyo-planner/src/extension/aggregate.rs:508-513 | crates/arroyo-planner/src/extension/window_fn.rs:74-79 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) crates/arroyo-worker/src/arrow/updating_cache.rs:161— crates/arroyo-worker/src/arrow/updating_cache.rs:161-166 | crates/arroyo-worker/src/arrow/updating_cache.rs:192-197 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) crates/arroyo-controller/src/schedulers/kubernetes/mod.rs:296— crates/arroyo-controller/src/schedulers/kubernetes/mod.rs:296-300 | crates/arroyo-controller/src/schedulers/kubernetes/mod.rs:337-343 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) crates/arroyo-rpc/src/config.rs:946— crates/arroyo-rpc/src/config.rs:946-950 | crates/arroyo-udf/arroyo-udf-common/src/parse.rs:216-220 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) crates/arroyo-state/src/tables/table_manager.rs:518— crates/arroyo-state/src/tables/table_manager.rs:518-522 | crates/arroyo-state/src/tables/table_manager.rs:556-560 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) crates/arroyo-worker/src/engine.rs:312— crates/arroyo-worker/src/engine.rs:312-316 | crates/arroyo-worker/src/engine.rs:317-321 — 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.
Change coupling: mod.rs ↔ lib.rs crates/arroyo-controller/src/schedulers/mod.rs— `crates/arroyo-controller/src/schedulers/mod.rs` and `crates/arroyo-node/src/lib.rs` change together 69% of the time (9 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `48879331` Don't schedule on workers with old run ids (#914); `1218232a` mTLS and key-based authentication (#908); `6653b6f3` Add TLS support for all services (#899) — run `git show` on any of them.
Change coupling: expiring_time_key_map.rs ↔ engine.rs crates/arroyo-state/src/tables/expiring_time_key_map.rs— `crates/arroyo-state/src/tables/expiring_time_key_map.rs` and `crates/arroyo-worker/src/engine.rs` change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `29ceaa60` implement window functions over already windowed inputs. (#563); `1e3ec854` Queue based on batch size, rather than batch count (#556); `2c86e009` Support non-windowed inner joins. (#510) (at that commit the files were still `arroyo-state/src/tables/expiring_time_key_map.rs` and `arroyo-worker/src/engine.rs`) — run `git show` on any of them.
Change coupling: table_manager.rs ↔ engine.rs crates/arroyo-state/src/tables/table_manager.rs— `crates/arroyo-state/src/tables/table_manager.rs` and `crates/arroyo-worker/src/engine.rs` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `9c7f1bd3` Add optional state_url and tags to pipelines (#1053); `a6e798ac` Structured error handling (part 2) (#980); `2c86e009` Support non-windowed inner joins. (#510) (at that commit the files were still `arroyo-state/src/tables/table_manager.rs` and `arroyo-worker/src/engine.rs`) — run `git show` on any of them.
Duplicated block (13–14 lines × 3) crates/arroyo-connectors/src/filesystem/iceberg.rs:248— crates/arroyo-connectors/src/filesystem/iceberg.rs:248-261 | crates/arroyo-connectors/src/preview/mod.rs:95-107 | crates/arroyo-connectors/src/webhook/mod.rs:162-174 — before extracting anything, compare `crates/arroyo-connectors/src/filesystem/iceberg.rs` and `crates/arroyo-connectors/src/webhook/mod.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 34 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13–14 lines × 3) crates/arroyo-connectors/src/polling_http/operator.rs:215— crates/arroyo-connectors/src/polling_http/operator.rs:215-227 | crates/arroyo-connectors/src/sse/operator.rs:224-237 | crates/arroyo-connectors/src/websocket/operator.rs:249-261 — `crates/arroyo-connectors/src/sse/operator.rs` and `crates/arroyo-connectors/src/websocket/operator.rs` 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 3 separate duplicated blocks between them, totalling at least 41 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.
Duplicated block (13–14 lines × 3) crates/arroyo-state/src/tables/table_manager.rs:501— crates/arroyo-state/src/tables/table_manager.rs:501-513 | crates/arroyo-state/src/tables/table_manager.rs:539-551 | crates/arroyo-state/src/tables/table_manager.rs:576-589 — 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 (12–13 lines × 2) crates/arroyo-connectors/src/fluvio/mod.rs:93— crates/arroyo-connectors/src/fluvio/mod.rs:93-105 | crates/arroyo-connectors/src/kinesis/mod.rs:135-146 — `crates/arroyo-connectors/src/fluvio/mod.rs` and `crates/arroyo-connectors/src/kinesis/mod.rs` 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 8 separate duplicated blocks between them, totalling at least 82 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.
Duplicated block (12–13 lines × 2) crates/arroyo-planner/src/extension/aggregate.rs:79— crates/arroyo-planner/src/extension/aggregate.rs:79-90 | crates/arroyo-planner/src/extension/aggregate.rs:127-139 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12–13 lines × 2) crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs:617— crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs:617-629 | crates/arroyo-worker/src/arrow/tumbling_aggregating_window.rs:269-280 — before extracting anything, compare `crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs` and `crates/arroyo-worker/src/arrow/tumbling_aggregating_window.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 105 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 3) crates/arroyo-connectors/src/kafka/mod.rs:358— crates/arroyo-connectors/src/kafka/mod.rs:358-368 | crates/arroyo-connectors/src/mqtt/mod.rs:259-269 | crates/arroyo-connectors/src/nats/mod.rs:294-304 — `crates/arroyo-connectors/src/kafka/mod.rs` and `crates/arroyo-connectors/src/mqtt/mod.rs` 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 12 separate duplicated blocks between them, totalling at least 114 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.
Duplicated block (11 lines × 3) crates/arroyo-connectors/src/polling_http/mod.rs:198— crates/arroyo-connectors/src/polling_http/mod.rs:198-208 | crates/arroyo-connectors/src/sse/mod.rs:83-93 | crates/arroyo-connectors/src/websocket/mod.rs:225-235 — `crates/arroyo-connectors/src/sse/mod.rs` and `crates/arroyo-connectors/src/websocket/mod.rs` 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 5 separate duplicated blocks between them, totalling at least 54 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.
Duplicated block (11 lines × 3) crates/arroyo-connectors/src/confluent/mod.rs:105— crates/arroyo-connectors/src/confluent/mod.rs:105-115 | crates/arroyo-connectors/src/kafka/mod.rs:182-192 | crates/arroyo-connectors/src/mqtt/mod.rs:139-149 — `crates/arroyo-connectors/src/confluent/mod.rs` and `crates/arroyo-connectors/src/kafka/mod.rs` 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 4 separate duplicated blocks between them, totalling at least 33 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.
AC2 · Forms & labels· <NumberInput> field component without a label · ×2
<NumberInput> field component without a label webui/src/components/StartPipelineModal.tsx:75— This UI-library field component has no label / aria-label / aria-labelledby / id / name — and neither does anything it renders — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<NumberInput> field component without a label webui/src/routes/pipelines/PipelineConfigModal.tsx:69— This UI-library field component has no label / aria-label / aria-labelledby / id / name — and neither does anything it renders — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
arroyo_formats::avro::ser::serialize_column (cyclomatic 41) crates/arroyo-formats/src/avro/ser.rs:63— arroyo_formats::avro::ser::serialize_column has cyclomatic complexity 41 (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.
arroyo_formats::proto::de::proto_value_to_json (cyclomatic 21) crates/arroyo-formats/src/proto/de.rs:46— arroyo_formats::proto::de::proto_value_to_json has cyclomatic complexity 21 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
WorkerJobController::start_inner (cyclomatic 30) crates/arroyo-worker/src/job_controller/controller.rs:292— WorkerJobController::start_inner has cyclomatic complexity 30 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
WorkerJobController::progress (cyclomatic 26) crates/arroyo-worker/src/job_controller/controller.rs:552— WorkerJobController::progress has cyclomatic complexity 26 (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.
arroyo_connectors::filesystem::sink::iceberg::metadata::get_parquet_stat_min_as_datum (cyclomatic 22) crates/arroyo-connectors/src/filesystem/sink/iceberg/metadata.rs:286— arroyo_connectors::filesystem::sink::iceberg::metadata::get_parquet_stat_min_as_datum has cyclomatic complexity 22 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing. This shape REPEATS in the file: one other method here (arroyo_connectors::filesystem::sink::iceberg::metadata::get_parquet_stat_max_as_datum) 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.
arroyo_connectors::filesystem::sink::iceberg::metadata::get_parquet_stat_max_as_datum (cyclomatic 22) crates/arroyo-connectors/src/filesystem/sink/iceberg/metadata.rs:366— arroyo_connectors::filesystem::sink::iceberg::metadata::get_parquet_stat_max_as_datum has cyclomatic complexity 22 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing. This shape REPEATS in the file: one other method here (arroyo_connectors::filesystem::sink::iceberg::metadata::get_parquet_stat_min_as_datum) 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.
XxxComment crates/arroyo-udf/arroyo-udf-python/src/pyarrow.rs:113— // // XXX: it is slow to call eval every time — 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.
XxxComment crates/arroyo-udf/arroyo-udf-python/src/interpreter.rs:34— // XXX: import the `decimal` module in the main interpreter before creating sub-interpreters. — 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.
IncrementalAggregatingFunc::initialize (cognitive 52) REDACTED:446— IncrementalAggregatingFunc::initialize has cognitive complexity 52 (threshold 15). Drivers by points: if/else 15 (38 pts), loops 7 (14 pts) (nesting depth added 30). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
IncrementalAggregatingFunc::flush (cognitive 21) REDACTED:637— IncrementalAggregatingFunc::flush has cognitive complexity 21 (threshold 15). Drivers by points: loops 7 (12 pts), if/else 5 (9 pts) (nesting depth added 9). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
WorkerJobController::start_inner (cognitive 46) crates/arroyo-worker/src/job_controller/controller.rs:292— WorkerJobController::start_inner has cognitive complexity 46 (threshold 15). Drivers by points: match/switch 7 (19 pts), if/else 4 (14 pts), loops 6 (13 pts) (nesting depth added 29). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WorkerJobController::progress (cognitive 25) crates/arroyo-worker/src/job_controller/controller.rs:552— WorkerJobController::progress has cognitive complexity 25 (threshold 15). Drivers by points: if/else 12, boolean chains 9, match/switch 2 (4 pts) (nesting depth added 2). 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.
arroyo_api::pipelines::compile_sql (cognitive 32) crates/arroyo-api/src/pipelines.rs:61— arroyo_api::pipelines::compile_sql has cognitive complexity 32 (threshold 15). Drivers by points: if/else 8 (22 pts), loops 4 (5 pts), match/switch 2 (5 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.
arroyo_api::pipelines::create_pipeline_int (cognitive 23) crates/arroyo-api/src/pipelines.rs:300— arroyo_api::pipelines::create_pipeline_int has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (13 pts), loops 3 (9 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
KinesisSourceFunc::run_int (cognitive 27) crates/arroyo-connectors/src/kinesis/source.rs:352— KinesisSourceFunc::run_int has cognitive complexity 27 (threshold 15). Drivers by points: match/switch 4 (12 pts), if/else 3 (10 pts), loops 2 (5 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.
KinesisSourceFunc::read_data_from_shard_iterator (cognitive 21) crates/arroyo-connectors/src/kinesis/source.rs:267— KinesisSourceFunc::read_data_from_shard_iterator has cognitive complexity 21 (threshold 15). Drivers by points: if/else 4 (14 pts), match/switch 2 (5 pts), boolean chains 1, loops 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.
arroyo_planner::parse_and_get_arrow_program (cognitive 27) crates/arroyo-planner/src/lib.rs:834— arroyo_planner::parse_and_get_arrow_program has cognitive complexity 27 (threshold 15). Drivers by points: if/else 8 (17 pts), match/switch 3 (7 pts), loops 3 (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.
arroyo_planner::find_window (cognitive 19) crates/arroyo-planner/src/lib.rs:642— arroyo_planner::find_window has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (16 pts), match/switch 2 (3 pts) (nesting depth added 11). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
arroyo_connectors::filesystem::sink::iceberg::map_iceberg_error (cognitive 24) crates/arroyo-connectors/src/filesystem/sink/iceberg/mod.rs:96— arroyo_connectors::filesystem::sink::iceberg::map_iceberg_error has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (20 pts), match/switch 2 (3 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
arroyo_connectors::mqtt::create_connection (cognitive 17) crates/arroyo-connectors/src/mqtt/mod.rs:407— arroyo_connectors::mqtt::create_connection has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (11 pts), loops 2 (6 pts) (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
Duplicated block (20 lines × 2) crates/arroyo-connectors/src/filesystem/delta.rs:96— crates/arroyo-connectors/src/filesystem/delta.rs:96-115 | crates/arroyo-connectors/src/filesystem/mod.rs:229-248 — before extracting anything, compare `crates/arroyo-connectors/src/filesystem/delta.rs` and `crates/arroyo-connectors/src/filesystem/mod.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 87 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 × 2) crates/arroyo-connectors/src/kafka/source/mod.rs:275— crates/arroyo-connectors/src/kafka/source/mod.rs:275-294 | crates/arroyo-connectors/src/mqtt/source/mod.rs:197-216 — 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 (18 lines × 2) crates/arroyo-connectors/src/impulse/operator.rs:143— crates/arroyo-connectors/src/impulse/operator.rs:143-160 | crates/arroyo-connectors/src/impulse/operator.rs:169-186 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (18 lines × 2) crates/arroyo-state/src/tables/table_manager.rs:418— crates/arroyo-state/src/tables/table_manager.rs:418-435 | crates/arroyo-state/src/tables/table_manager.rs:459-476 — 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) crates/arroyo-connectors/src/filesystem/delta.rs:116— crates/arroyo-connectors/src/filesystem/delta.rs:116-130 | crates/arroyo-connectors/src/filesystem/mod.rs:249-263 — before extracting anything, compare `crates/arroyo-connectors/src/filesystem/delta.rs` and `crates/arroyo-connectors/src/filesystem/mod.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 2) crates/arroyo-connectors/src/filesystem/sink/two_phase_committer.rs:145— crates/arroyo-connectors/src/filesystem/sink/two_phase_committer.rs:145-159 | crates/arroyo-connectors/src/filesystem/sink/v2/mod.rs:463-477 — 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) crates/arroyo-datastream/src/logical.rs:533— crates/arroyo-datastream/src/logical.rs:533-546 | crates/arroyo-datastream/src/logical.rs:556-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 (14 lines × 2) crates/arroyo-connectors/src/polling_http/mod.rs:75— crates/arroyo-connectors/src/polling_http/mod.rs:75-88 | crates/arroyo-connectors/src/webhook/mod.rs:64-77 — `crates/arroyo-connectors/src/polling_http/mod.rs` and `crates/arroyo-connectors/src/webhook/mod.rs` 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 4 separate duplicated blocks between them, totalling at least 35 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.
Duplicated block (11 lines × 2) crates/arroyo-connectors/src/filesystem/sink/mod.rs:358— crates/arroyo-connectors/src/filesystem/sink/mod.rs:358-368 | crates/arroyo-connectors/src/filesystem/sink/mod.rs:385-395 — 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) crates/arroyo-planner/src/extension/aggregate.rs:95— crates/arroyo-planner/src/extension/aggregate.rs:95-105 | crates/arroyo-planner/src/extension/aggregate.rs:145-155 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 3) crates/arroyo-planner/src/extension/aggregate.rs:96— crates/arroyo-planner/src/extension/aggregate.rs:96-105 | crates/arroyo-planner/src/extension/aggregate.rs:146-155 | crates/arroyo-planner/src/extension/aggregate.rs:268-277 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 3) crates/arroyo-connectors/src/kinesis/mod.rs:95— crates/arroyo-connectors/src/kinesis/mod.rs:95-104 | crates/arroyo-connectors/src/nats/mod.rs:252-262 | crates/arroyo-connectors/src/rabbitmq/mod.rs:186-196 — `crates/arroyo-connectors/src/kinesis/mod.rs` and `crates/arroyo-connectors/src/nats/mod.rs` 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 8 separate duplicated blocks between them, totalling at least 81 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.
Duplicated block (6 lines × 4) crates/arroyo-operator/src/context.rs:522— crates/arroyo-operator/src/context.rs:522-527 | crates/arroyo-worker/src/arrow/instant_join.rs:151-156 | crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs:611-616 | crates/arroyo-worker/src/arrow/tumbling_aggregating_window.rs:263-268 — before extracting anything, compare `crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs` and `crates/arroyo-worker/src/arrow/tumbling_aggregating_window.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 105 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 4) crates/arroyo-connectors/src/confluent/mod.rs:122— crates/arroyo-connectors/src/confluent/mod.rs:122-127 | crates/arroyo-connectors/src/kafka/mod.rs:318-323 | crates/arroyo-connectors/src/kinesis/mod.rs:72-77 | crates/arroyo-connectors/src/mqtt/mod.rs:237-242 — `crates/arroyo-connectors/src/confluent/mod.rs` and `crates/arroyo-connectors/src/kafka/mod.rs` 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 4 separate duplicated blocks between them, totalling at least 33 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.
Outbound HTTP without resilience crates/arroyo-connectors/src/filesystem/iceberg.rs:37— `reqwest::ClientBuilder::new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. 2 of the 7 files that make outbound calls are unbounded; the first 2 are listed.
Outbound HTTP without resilience crates/arroyo-server-common/src/lib.rs:222— `Client::new()` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Duplicated block (15 lines × 2 locations) webui/src/routes/not_found/ApiUnavailable.tsx:5— webui/src/routes/not_found/ApiUnavailable.tsx:5 · webui/src/routes/not_found/PageNotFound.tsx:5 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (15 lines × 2 locations) webui/src/routes/udfs/UdfsResourceTab.tsx:69— webui/src/routes/udfs/UdfsResourceTab.tsx:69 · webui/src/routes/udfs/UdfsResourceTab.tsx:102 — 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 (11 lines × 2 locations) webui/src/routes/connections/DefineSchema.tsx:443— webui/src/routes/connections/DefineSchema.tsx:443 · webui/src/routes/connections/DefineSchema.tsx:455 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (11 lines × 2 locations) webui/src/routes/connections/JsonForm.tsx:525— webui/src/routes/connections/JsonForm.tsx:525 · webui/src/routes/connections/JsonForm.tsx:647 — all 2 copies are in the same file, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.
AC2 · Forms & labels· <Textarea> field component without a label · ×1
<Textarea> field component without a label webui/src/routes/udfs/GlobalizeModal.tsx:125— This UI-library field component has no label / aria-label / aria-labelledby / id / name — and neither does anything it renders — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
AC3 · Page structure· Page without a main landmark · ×1
Page without a main landmark webui/index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it.
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 56 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.
CreatePipeline.CreatePipeline (cyclomatic 64) webui/src/routes/pipelines/CreatePipeline.tsx:75— CreatePipeline.CreatePipeline has cyclomatic complexity 64 (threshold 15). Of this number, 36 points are the body's own statements and 28 belong to 12 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.
ArroyoRewriter::f_up (cyclomatic 33) crates/arroyo-planner/src/plan/mod.rs:264— ArroyoRewriter::f_up has cyclomatic complexity 33 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Scheduling::next (cyclomatic 31) crates/arroyo-controller/src/states/scheduling.rs:369— Scheduling::next has cyclomatic complexity 31 (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.
JsonForm.FormInner (cyclomatic 31) webui/src/routes/connections/JsonForm.tsx:703— JsonForm.FormInner has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 2 of the 31 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 751, 728, 737, …). 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.
Converter::build_array (cyclomatic 30) crates/arroyo-udf/arroyo-udf-python/src/pyarrow.rs:150— Converter::build_array has cyclomatic complexity 30 (threshold 15). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
CheckpointDetails.CheckpointTimeline (cyclomatic 30) webui/src/components/CheckpointDetails.tsx:54— CheckpointDetails.CheckpointTimeline has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 1 of the 30 points is its own statement and the rest belongs to 8 function literals inside it that branch (lines 58, 102, 78, …). 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.
ConnectionTester.ConnectionTester (cyclomatic 28) webui/src/routes/connections/ConnectionTester.tsx:36— ConnectionTester.ConnectionTester has cyclomatic complexity 28 (threshold 15). Of this number, 22 points are the body's own statements and 6 belong to 5 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
KafkaSourceFunc::run_int (cyclomatic 26) crates/arroyo-connectors/src/kafka/source/mod.rs:153— KafkaSourceFunc::run_int 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.
NatsSourceFunc::run_int (cyclomatic 26) crates/arroyo-connectors/src/nats/source/mod.rs:323— NatsSourceFunc::run_int has cyclomatic complexity 26 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
LeaderRunning::next (cyclomatic 26) crates/arroyo-controller/src/states/leader_running.rs:29— LeaderRunning::next 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.
Checkpoints.Checkpoints (cyclomatic 26) webui/src/components/Checkpoints.tsx:91— Checkpoints.Checkpoints has cyclomatic complexity 26 (threshold 15). Of this number, 21 points are the body's own statements and 5 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.
RunningJobModel::handle_message (cyclomatic 25) crates/arroyo-worker/src/job_controller/model.rs:143— RunningJobModel::handle_message 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.
ConnectorTable::from_options (cyclomatic 24) crates/arroyo-planner/src/tables.rs:235— ConnectorTable::from_options 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.
PipelineOutputs.PipelineOutputs (cyclomatic 24) webui/src/routes/pipelines/PipelineOutputs.tsx:9— PipelineOutputs.PipelineOutputs has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 10 of the 24 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 111, 30, 63, …). 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.
PipelineDetails.PipelineDetails (cyclomatic 24) webui/src/routes/pipelines/PipelineDetails.tsx:69— PipelineDetails.PipelineDetails has cyclomatic complexity 24 (threshold 15). Of this number, 23 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.
WindowDetectingVisitor::f_up (cyclomatic 23) crates/arroyo-planner/src/plan/mod.rs:93— WindowDetectingVisitor::f_up has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SSESourceFunc::run_int (cyclomatic 21) crates/arroyo-connectors/src/sse/operator.rs:134— SSESourceFunc::run_int 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.
DefineSchema.SchemaFormatEditor (cyclomatic 21) webui/src/routes/connections/DefineSchema.tsx:25— DefineSchema.SchemaFormatEditor has cyclomatic complexity 21 (threshold 15). Of this number, 17 points are the body's own statements and 4 belong to one function literal 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.
arroyo_udf_common::parse::rust_to_arrow (cyclomatic 20) crates/arroyo-udf/arroyo-udf-common/src/parse.rs:61— arroyo_udf_common::parse::rust_to_arrow has cyclomatic complexity 20 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
AsyncMultipartFileSystemWriter::run (cyclomatic 19) crates/arroyo-connectors/src/filesystem/sink/mod.rs:813— AsyncMultipartFileSystemWriter::run 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.
KafkaTester::validate_schema (cyclomatic 19) crates/arroyo-connectors/src/kafka/mod.rs:598— KafkaTester::validate_schema 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.
MqttSourceFunc::run_int (cyclomatic 19) crates/arroyo-connectors/src/mqtt/source/mod.rs:90— MqttSourceFunc::run_int has cyclomatic complexity 19 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
arroyo_operator::operator::operator_run_behavior (cyclomatic 19) crates/arroyo-operator/src/operator.rs:940— arroyo_operator::operator::operator_run_behavior has cyclomatic complexity 19 (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.
IncrementalAggregatingFunc::initialize (cyclomatic 19) REDACTED:446— IncrementalAggregatingFunc::initialize 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.
WebsocketSourceFunc::run_int (cyclomatic 18) crates/arroyo-connectors/src/websocket/operator.rs:135— WebsocketSourceFunc::run_int has cyclomatic complexity 18 (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.
udf_state.getLocalUdfsContextValue (cyclomatic 18) webui/src/udf_state.ts:50— udf_state.getLocalUdfsContextValue has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 10 function literals inside it that branch (lines 111, 65, 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.
FluvioSourceFunc::run_int (cyclomatic 17) crates/arroyo-connectors/src/fluvio/source.rs:143— FluvioSourceFunc::run_int has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
RedisConnector::from_options (cyclomatic 17) crates/arroyo-connectors/src/redis/mod.rs:232— RedisConnector::from_options has cyclomatic complexity 17 (threshold 15). Of this number, 15 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
arroyo_planner::parse_and_get_arrow_program (cyclomatic 17) crates/arroyo-planner/src/lib.rs:834— arroyo_planner::parse_and_get_arrow_program has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
JsonForm.AutocompleteWidget (cyclomatic 17) webui/src/routes/connections/JsonForm.tsx:230— JsonForm.AutocompleteWidget has cyclomatic complexity 17 (threshold 15). Of this number, 14 points are the body's own statements and 3 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.
RabbitmqStreamSourceFunc::run_int (cyclomatic 16) crates/arroyo-connectors/src/rabbitmq/source.rs:91— RabbitmqStreamSourceFunc::run_int 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.
StateMachine::start (cyclomatic 16) crates/arroyo-controller/src/states/mod.rs:892— StateMachine::start has cyclomatic complexity 16 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
LogicalProgram::features (cyclomatic 16) crates/arroyo-datastream/src/logical.rs:397— LogicalProgram::features has cyclomatic complexity 16 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
CodeEditor.CodeEditor (cyclomatic 16) webui/src/routes/pipelines/CodeEditor.tsx:22— CodeEditor.CodeEditor 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 6 function literals inside it that branch (lines 86, 40, 80, …). 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.
FixmeComment crates/arroyo-udf/arroyo-udf-python/src/interpreter.rs:52— // FIXME: according to the 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.
CreatePipeline.CreatePipeline (cognitive 84) webui/src/routes/pipelines/CreatePipeline.tsx:75— CreatePipeline.CreatePipeline has cognitive complexity 84 (threshold 15). Drivers by points: if/else 41 (56 pts), boolean chains 14, ternaries 9 (10 pts), loops 2 (4 pts) (nesting depth added 18). Of this number, 39 points are the body's own statements and 45 belong to 12 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
arroyo_formats::avro::ser::serialize_column (cognitive 67) crates/arroyo-formats/src/avro/ser.rs:63— arroyo_formats::avro::ser::serialize_column has cognitive complexity 67 (threshold 15). Drivers by points: if/else 27 (52 pts), loops 5 (14 pts), match/switch 1 (nesting depth added 34). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
KafkaSourceFunc::run_int (cognitive 59) crates/arroyo-connectors/src/kafka/source/mod.rs:153— KafkaSourceFunc::run_int has cognitive complexity 59 (threshold 15). Drivers by points: if/else 10 (29 pts), match/switch 5 (19 pts), loops 3 (11 pts) (nesting depth added 41). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NatsSourceFunc::run_int (cognitive 58) crates/arroyo-connectors/src/nats/source/mod.rs:323— NatsSourceFunc::run_int has cognitive complexity 58 (threshold 15). Drivers by points: match/switch 9 (29 pts), if/else 4 (20 pts), loops 3 (9 pts) (nesting depth added 42). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
RunningJobModel::handle_message (cognitive 57) crates/arroyo-worker/src/job_controller/model.rs:143— RunningJobModel::handle_message has cognitive complexity 57 (threshold 15). Drivers by points: if/else 23 (48 pts), match/switch 2 (5 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 29). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SSESourceFunc::run_int (cognitive 56) crates/arroyo-connectors/src/sse/operator.rs:134— SSESourceFunc::run_int has cognitive complexity 56 (threshold 15). Drivers by points: if/else 10 (38 pts), match/switch 3 (12 pts), loops 3 (5 pts), boolean chains 1 (nesting depth added 39). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AsyncMultipartFileSystemWriter::run (cognitive 52) crates/arroyo-connectors/src/filesystem/sink/mod.rs:813— AsyncMultipartFileSystemWriter::run has cognitive complexity 52 (threshold 15). Drivers by points: if/else 9 (36 pts), loops 4 (11 pts), match/switch 2 (5 pts) (nesting depth added 37). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Scheduling::next (cognitive 51) crates/arroyo-controller/src/states/scheduling.rs:369— Scheduling::next has cognitive complexity 51 (threshold 15). Drivers by points: if/else 10 (27 pts), match/switch 9 (19 pts), loops 4, boolean chains 1 (nesting depth added 27). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WindowDetectingVisitor::f_up (cognitive 51) crates/arroyo-planner/src/plan/mod.rs:93— WindowDetectingVisitor::f_up has cognitive complexity 51 (threshold 15). Drivers by points: if/else 13 (36 pts), loops 3 (7 pts), match/switch 4 (7 pts), boolean chains 1 (nesting depth added 30). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
LeaderRunning::next (cognitive 50) crates/arroyo-controller/src/states/leader_running.rs:29— LeaderRunning::next has cognitive complexity 50 (threshold 15). Drivers by points: if/else 10 (30 pts), match/switch 5 (16 pts), boolean chains 3, loops 1 (nesting depth added 31). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
arroyo_operator::operator::operator_run_behavior (cognitive 42) crates/arroyo-operator/src/operator.rs:940— arroyo_operator::operator::operator_run_behavior has cognitive complexity 42 (threshold 15). Drivers by points: if/else 5 (17 pts), match/switch 4 (14 pts), loops 4 (10 pts), boolean chains 1 (nesting depth added 28). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TumblingAggregatingWindowFunc::handle_watermark (cognitive 42) crates/arroyo-worker/src/arrow/tumbling_aggregating_window.rs:321— TumblingAggregatingWindowFunc::handle_watermark has cognitive complexity 42 (threshold 15). Drivers by points: if/else 9 (26 pts), loops 4 (16 pts) (nesting depth added 29). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CheckpointDetails.CheckpointTimeline (cognitive 40) webui/src/components/CheckpointDetails.tsx:54— CheckpointDetails.CheckpointTimeline has cognitive complexity 40 (threshold 15). Drivers by points: if/else 11 (18 pts), boolean chains 13, loops 4 (7 pts), ternaries 2 (nesting depth added 10). Most of this is not in the body itself: 0 of the 40 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 58, 102, 78, …). 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.
KafkaTester::validate_schema (cognitive 38) crates/arroyo-connectors/src/kafka/mod.rs:598— KafkaTester::validate_schema has cognitive complexity 38 (threshold 15). Drivers by points: if/else 15 (34 pts), match/switch 2 (4 pts) (nesting depth added 21). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
MqttSourceFunc::run_int (cognitive 37) crates/arroyo-connectors/src/mqtt/source/mod.rs:90— MqttSourceFunc::run_int has cognitive complexity 37 (threshold 15). Drivers by points: match/switch 5 (18 pts), if/else 5 (13 pts), loops 2 (6 pts) (nesting depth added 25). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
JsonForm.FormInner (cognitive 36) webui/src/routes/connections/JsonForm.tsx:703— JsonForm.FormInner has cognitive complexity 36 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 12, ternaries 2 (7 pts), match/switch 1 (2 pts) (nesting depth added 12). Most of this is not in the body itself: 1 of the 36 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 751, 728, 737, …). 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.
RedisWriter::start (cognitive 35) crates/arroyo-connectors/src/redis/sink.rs:114— RedisWriter::start has cognitive complexity 35 (threshold 15). Drivers by points: if/else 7 (23 pts), match/switch 3 (9 pts), boolean chains 2, loops 1 (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ConnectorTable::from_options (cognitive 35) crates/arroyo-planner/src/tables.rs:235— ConnectorTable::from_options has cognitive complexity 35 (threshold 15). Drivers by points: if/else 18 (26 pts), match/switch 2 (5 pts), boolean chains 4 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PollingHttpSourceFunc::run_int (cognitive 31) crates/arroyo-connectors/src/polling_http/operator.rs:169— PollingHttpSourceFunc::run_int has cognitive complexity 31 (threshold 15). Drivers by points: if/else 6 (19 pts), match/switch 2 (7 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WebsocketSourceFunc::run_int (cognitive 31) crates/arroyo-connectors/src/websocket/operator.rs:135— WebsocketSourceFunc::run_int has cognitive complexity 31 (threshold 15). Drivers by points: if/else 5 (13 pts), match/switch 3 (12 pts), loops 4 (6 pts) (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.
Converter::build_array (cognitive 30) crates/arroyo-udf/arroyo-udf-python/src/pyarrow.rs:150— Converter::build_array has cognitive complexity 30 (threshold 15). Drivers by points: loops 6 (17 pts), if/else 5 (12 pts), match/switch 1 (nesting depth added 18). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
FluvioSourceFunc::run_int (cognitive 29) crates/arroyo-connectors/src/fluvio/source.rs:143— FluvioSourceFunc::run_int has cognitive complexity 29 (threshold 15). Drivers by points: if/else 4 (12 pts), match/switch 4 (12 pts), loops 2 (5 pts) (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.
Table::try_from_statement (cognitive 29) crates/arroyo-planner/src/tables.rs:772— Table::try_from_statement has cognitive complexity 29 (threshold 15). Drivers by points: if/else 7 (16 pts), match/switch 5 (13 pts) (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RabbitmqStreamSourceFunc::run_int (cognitive 28) crates/arroyo-connectors/src/rabbitmq/source.rs:91— RabbitmqStreamSourceFunc::run_int has cognitive complexity 28 (threshold 15). Drivers by points: if/else 4 (15 pts), match/switch 4 (12 pts), loops 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.
LookupJoin::process_batch (cognitive 28) crates/arroyo-worker/src/arrow/lookup_join.rs:53— LookupJoin::process_batch has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (16 pts), loops 6 (11 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Checkpoints.Checkpoints (cognitive 28) webui/src/components/Checkpoints.tsx:91— Checkpoints.Checkpoints has cognitive complexity 28 (threshold 15). Drivers by points: if/else 11 (12 pts), boolean chains 8, ternaries 5 (8 pts) (nesting depth added 4). Of this number, 23 points are the body's own statements and 5 belong to 3 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
KubernetesScheduler::make_pod (cognitive 27) crates/arroyo-controller/src/schedulers/kubernetes/mod.rs:75— KubernetesScheduler::make_pod has cognitive complexity 27 (threshold 15). Drivers by points: if/else 6 (22 pts), loops 3 (4 pts), match/switch 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Program::from_logical (cognitive 26) crates/arroyo-worker/src/engine.rs:210— Program::from_logical has cognitive complexity 26 (threshold 15). Drivers by points: loops 7 (15 pts), if/else 4 (6 pts), match/switch 2 (4 pts), boolean chains 1 (nesting depth added 12). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
FileSystemSinkV2::handle_commit (cognitive 24) crates/arroyo-connectors/src/filesystem/sink/v2/mod.rs:769— FileSystemSinkV2::handle_commit has cognitive complexity 24 (threshold 15). Drivers by points: loops 6 (10 pts), if/else 4 (9 pts), match/switch 2 (5 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.
LeaderRestarting::next (cognitive 24) crates/arroyo-controller/src/states/leader_restarting.rs:24— LeaderRestarting::next has cognitive complexity 24 (threshold 15). Drivers by points: if/else 5 (14 pts), match/switch 3 (8 pts), loops 1 (2 pts) (nesting depth added 15). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
PipelineDetails.PipelineDetails (cognitive 24) webui/src/routes/pipelines/PipelineDetails.tsx:69— PipelineDetails.PipelineDetails has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 8 (10 pts), if/else 7 (8 pts), boolean chains 6 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
ProcessScheduler::start_workers (cognitive 23) crates/arroyo-controller/src/schedulers/mod.rs:113— ProcessScheduler::start_workers has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (16 pts), match/switch 2 (4 pts), loops 2 (3 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UnnestRewriter::f_up (cognitive 23) crates/arroyo-planner/src/rewriters.rs:368— UnnestRewriter::f_up has cognitive complexity 23 (threshold 15). Drivers by points: if/else 14 (21 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.
BackendFlusher::flush_iteration (cognitive 22) crates/arroyo-state/src/tables/table_manager.rs:95— BackendFlusher::flush_iteration has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 4 (5 pts), match/switch 2 (5 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.
ImpulseSourceFunc::run (cognitive 21) crates/arroyo-connectors/src/impulse/operator.rs:96— ImpulseSourceFunc::run has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (15 pts), match/switch 2 (5 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ConnectionTester.ConnectionTester (cognitive 21) webui/src/routes/connections/ConnectionTester.tsx:36— ConnectionTester.ConnectionTester has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 14, if/else 6, ternaries 1. Of this number, 15 points are the body's own statements and 6 belong to 5 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
IcebergFileMetadata::from_parquet (cognitive 20) crates/arroyo-connectors/src/filesystem/sink/iceberg/metadata.rs:48— IcebergFileMetadata::from_parquet has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (16 pts), loops 3 (4 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.
arroyo_node::start_server (cognitive 20) crates/arroyo-node/src/lib.rs:264— arroyo_node::start_server has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (10 pts), match/switch 2 (6 pts), loops 2 (4 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.
ArroyoRewriter::f_up (cognitive 20) crates/arroyo-planner/src/plan/mod.rs:264— ArroyoRewriter::f_up has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 1 (2 pts), boolean chains 1, match/switch 1 (nesting depth added 10). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ParsedUdf::try_parse (cognitive 20) crates/arroyo-udf/arroyo-udf-common/src/parse.rs:257— ParsedUdf::try_parse has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (15 pts), match/switch 2 (3 pts), boolean chains 1, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FileCheckpointData::fmt (cognitive 19) crates/arroyo-connectors/src/filesystem/sink/mod.rs:329— FileCheckpointData::fmt has cognitive complexity 19 (threshold 15). Drivers by points: loops 4 (8 pts), if/else 4 (6 pts), match/switch 3 (5 pts) (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
arroyo_udf_common::parse::rust_to_arrow (cognitive 19) crates/arroyo-udf/arroyo-udf-common/src/parse.rs:61— arroyo_udf_common::parse::rust_to_arrow has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (12 pts), match/switch 3 (7 pts) (nesting depth added 11). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
udf_state.getLocalUdfsContextValue (cognitive 19) webui/src/udf_state.ts:50— udf_state.getLocalUdfsContextValue has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 6, ternaries 4 (nesting depth added 1). Most of this is not in the body itself: 0 of the 19 points are its own statements and the rest belongs to 10 function literals inside it that branch (lines 111, 65, 78, …). 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.
PipelineOutputs.PipelineOutputs (cognitive 19) webui/src/routes/pipelines/PipelineOutputs.tsx:9— PipelineOutputs.PipelineOutputs has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 8, ternaries 1 (nesting depth added 1). Most of this is not in the body itself: 4 of the 19 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 111, 30, 63, …). 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.
NexmarkSourceFunc::run (cognitive 18) crates/arroyo-connectors/src/nexmark/operator.rs:248— NexmarkSourceFunc::run has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (10 pts), match/switch 2 (7 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SessionAggregatingWindowFunc::results_at_watermark (cognitive 18) crates/arroyo-worker/src/arrow/session_aggregating_window.rs:99— SessionAggregatingWindowFunc::results_at_watermark has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (15 pts), loops 2 (3 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.
JsonForm.AutocompleteWidget (cognitive 18) webui/src/routes/connections/JsonForm.tsx:230— JsonForm.AutocompleteWidget has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 6 (8 pts), boolean chains 7, if/else 3 (nesting depth added 2). Of this number, 16 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, 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.
FileSystemSourceFunc::read_line_file (cognitive 17) crates/arroyo-connectors/src/filesystem/source.rs:336— FileSystemSourceFunc::read_line_file has cognitive complexity 17 (threshold 15). Drivers by points: if/else 3 (11 pts), match/switch 2 (5 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RedisConnector::from_options (cognitive 17) crates/arroyo-connectors/src/redis/mod.rs:232— RedisConnector::from_options has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 5 (9 pts), if/else 2 (4 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 7). Of this number, 15 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
WebhookSinkFunc::process_batch (cognitive 17) crates/arroyo-connectors/src/webhook/operator.rs:41— WebhookSinkFunc::process_batch has cognitive complexity 17 (threshold 15). Drivers by points: if/else 3 (10 pts), loops 2 (3 pts), match/switch 1 (3 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
arroyo_controller::leader_manager::handle_leader_stopping (cognitive 17) crates/arroyo-controller/src/leader_manager.rs:174— arroyo_controller::leader_manager::handle_leader_stopping has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 3 (9 pts), if/else 2 (7 pts), loops 1 (nesting depth added 11). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
BufferDecoder::flush (cognitive 17) crates/arroyo-formats/src/de.rs:202— BufferDecoder::flush has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (8 pts), match/switch 3 (6 pts), loops 1 (3 pts) (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ChainedOperator::handle_control_message (cognitive 17) crates/arroyo-operator/src/operator.rs:669— ChainedOperator::handle_control_message has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (16 pts), match/switch 1 (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ArroyoCredentialProvider::get_credential (cognitive 17) crates/arroyo-storage/src/aws.rs:111— ArroyoCredentialProvider::get_credential has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (14 pts), boolean chains 2, match/switch 1 (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
arroyo_worker::engine::construct_node (cognitive 17) crates/arroyo-worker/src/engine.rs:808— arroyo_worker::engine::construct_node has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (15 pts), loops 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
data_fetching.useConnectionTableTest (cognitive 17) webui/src/lib/data_fetching.ts:659— data_fetching.useConnectionTableTest has cognitive complexity 17 (threshold 15). Drivers by points: error handling 2 (6 pts), if/else 3 (6 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SchemaEditor.SchemaEditor (cognitive 17) webui/src/routes/connections/SchemaEditor.tsx:21— SchemaEditor.SchemaEditor has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (11 pts), boolean chains 3, ternaries 2 (3 pts) (nesting depth added 2). Most of this is not in the body itself: 8 of the 17 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 44, 167). 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.
MqttSinkFunc::on_start (cognitive 16) crates/arroyo-connectors/src/mqtt/sink/mod.rs:49— MqttSinkFunc::on_start has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 3 (11 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 10). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
arroyo_server_common::init_logging_with_filter (cognitive 16) crates/arroyo-server-common/src/lib.rs:84— arroyo_server_common::init_logging_with_filter has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (11 pts), loops 2 (4 pts), match/switch 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TimeTableCompactor::compact_files (cognitive 16) crates/arroyo-state/src/tables/expiring_time_key_map.rs:477— TimeTableCompactor::compact_files has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 3 (7 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.
CheckpointState::checkpoint_finished (cognitive 16) crates/arroyo-worker/src/job_controller/checkpoint_state.rs:271— CheckpointState::checkpoint_finished has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (7 pts), loops 2 (6 pts), match/switch 1 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WorkerState::run_control_loop (cognitive 16) crates/arroyo-worker/src/lib.rs:467— WorkerState::run_control_loop has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (10 pts), match/switch 2 (5 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.
DefineSchema.SchemaFormatEditor (cognitive 16) webui/src/routes/connections/DefineSchema.tsx:25— DefineSchema.SchemaFormatEditor has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8, boolean chains 6, match/switch 2. Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
CreateProfile.CreateProfile (cognitive 16) webui/src/routes/connections/CreateProfile.tsx:18— CreateProfile.CreateProfile has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9, ternaries 3 (4 pts), boolean chains 3 (nesting depth added 1). Most of this is not in the body itself: 4 of the 16 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 36, 65, 79, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D22 · Internal API Consistency· Inconsistent parameter naming for identical signatures. Most connectors use `options` (plural), while ConfluentConnector uses `opts` (abbreviated). · ×1
Inconsistent parameter naming for identical signatures. Most connectors use `options` (plural), while ConfluentConnector uses `opts` (abbreviated). — Standardize to `options` across all connector implementations for consistency. (signatures: arroyo_connectors.kafka.KafkaConnector.connection_from_options(options: ConnectorOptions): Result | arroyo_connectors.mqtt.MqttConnector.connection_from_options(options: ConnectorOptions): Result | arroyo_connectors.nats.NatsConnector.connection_from_options(options: ConnectorOptions): Result | arroyo_connectors.confluent.ConfluentConnector.connection_from_options(opts: ConnectorOptions): Result)
D22 · Internal API Consistency· Inconsistent parameter naming for identical signatures. Most connectors use `options` (plural), while ConfluentConnector uses `opts` (abbreviated). Note · ×1
Inconsistent parameter naming for identical signatures. Most connectors use `options` (plural), while ConfluentConnector uses `opts` (abbreviated). Note: ConfluentConnector does not expose `table_from_options`, but the inconsistency in `connection_from_options` is sufficient to flag the naming convention drift. — Ensure all connectors follow the same naming convention for `ConnectorOptions` parameters. If `opts` is preferred for brevity, apply it everywhere; otherwise, use `options`. (signatures: arroyo_connectors.kafka.KafkaConnector.table_from_options(options: ConnectorOptions): Result | arroyo_connectors.mqtt.MqttConnector.table_from_options(options: ConnectorOptions): Result | arroyo_connectors.nats.NatsConnector.table_from_options(options: ConnectorOptions): Result)
TooManyMethods: StorageProvider crates/arroyo-storage/src/lib.rs:56— TooManyMethods — 34 methods. The bar is 30 methods; this is 4 over it, 1.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication· Near-duplicate member family (4 members, 15 shared lines) · ×1
Near-duplicate member family (4 members, 15 shared lines) crates/arroyo-connectors/src/filesystem/delta.rs:77— crates/arroyo-connectors/src/filesystem/delta.rs:77-130 | crates/arroyo-connectors/src/filesystem/mod.rs:204-263 | crates/arroyo-connectors/src/redis/mod.rs:397-434 | crates/arroyo-connectors/src/single_file/mod.rs:86-117 — These 4 members are variants of one another: a block of 15 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (5 members, 50+ identical tokens) crates/arroyo-state/src/tables/table_manager.rs:415— crates/arroyo-state/src/tables/table_manager.rs:415-452 | crates/arroyo-state/src/tables/table_manager.rs:457-493 | crates/arroyo-state/src/tables/table_manager.rs:499-531 | crates/arroyo-state/src/tables/table_manager.rs:537-569 | crates/arroyo-state/src/tables/table_manager.rs:574-611 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (4 members, 50+ identical tokens) crates/arroyo-connectors/src/confluent/mod.rs:170— crates/arroyo-connectors/src/confluent/mod.rs:170-182 | crates/arroyo-connectors/src/kafka/mod.rs:356-368 | crates/arroyo-connectors/src/mqtt/mod.rs:257-269 | crates/arroyo-connectors/src/nats/mod.rs:292-304 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Duplicated block (29 lines × 2) crates/arroyo-connectors/src/nats/source/mod.rs:438— crates/arroyo-connectors/src/nats/source/mod.rs:438-466 | crates/arroyo-connectors/src/nats/source/mod.rs:495-523 — 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 (25–29 lines × 2) crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs:462— crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs:462-486 | crates/arroyo-worker/src/arrow/tumbling_aggregating_window.rs:123-151 — before extracting anything, compare `crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs` and `crates/arroyo-worker/src/arrow/tumbling_aggregating_window.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 105 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 (26 lines × 2) crates/arroyo-planner/src/plan/aggregate.rs:33— crates/arroyo-planner/src/plan/aggregate.rs:33-58 | crates/arroyo-planner/src/plan/aggregate.rs:228-253 — 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 (25 lines × 2) crates/arroyo-api/src/jobs.rs:406— crates/arroyo-api/src/jobs.rs:406-430 | crates/arroyo-api/src/jobs.rs:470-494 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (19 lines × 3) crates/arroyo-connectors/src/polling_http/operator.rs:99— crates/arroyo-connectors/src/polling_http/operator.rs:99-117 | crates/arroyo-connectors/src/sse/operator.rs:114-132 | crates/arroyo-connectors/src/websocket/operator.rs:99-117 — `crates/arroyo-connectors/src/sse/operator.rs` and `crates/arroyo-connectors/src/websocket/operator.rs` 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 3 separate duplicated blocks between them, totalling at least 41 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.
Duplicated block (17 lines × 3) crates/arroyo-api/src/jobs.rs:411— crates/arroyo-api/src/jobs.rs:411-427 | crates/arroyo-api/src/jobs.rs:475-491 | crates/arroyo-api/src/metrics.rs:45-61 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (14–16 lines × 3) crates/arroyo-connectors/src/blackhole/mod.rs:94— crates/arroyo-connectors/src/blackhole/mod.rs:94-107 | crates/arroyo-connectors/src/impulse/mod.rs:148-163 | crates/arroyo-connectors/src/nexmark/mod.rs:199-214 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (13–16 lines × 2) crates/arroyo-formats/src/avro/ser.rs:223— crates/arroyo-formats/src/avro/ser.rs:223-238 | crates/arroyo-formats/src/avro/ser.rs:254-266 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14–15 lines × 3) crates/arroyo-connectors/src/kafka/source/mod.rs:271— crates/arroyo-connectors/src/kafka/source/mod.rs:271-285 | crates/arroyo-connectors/src/kinesis/source.rs:402-415 | crates/arroyo-connectors/src/mqtt/source/mod.rs:193-207 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (13–14 lines × 8) crates/arroyo-connectors/src/filesystem/delta.rs:115— crates/arroyo-connectors/src/filesystem/delta.rs:115-128 | crates/arroyo-connectors/src/filesystem/mod.rs:248-261 | crates/arroyo-connectors/src/fluvio/mod.rs:154-166 | crates/arroyo-connectors/src/kafka/mod.rs:230-242 | crates/arroyo-connectors/src/kinesis/mod.rs:112-124 | crates/arroyo-connectors/src/mqtt/mod.rs:187-199 | crates/arroyo-connectors/src/nats/mod.rs:270-282 | crates/arroyo-connectors/src/rabbitmq/mod.rs:204-216 — before extracting anything, compare `crates/arroyo-connectors/src/filesystem/delta.rs` and `crates/arroyo-connectors/src/filesystem/mod.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (12–14 lines × 2) crates/arroyo-connectors/src/filesystem/sink/local.rs:96— crates/arroyo-connectors/src/filesystem/sink/local.rs:96-107 | crates/arroyo-connectors/src/filesystem/sink/mod.rs:934-947 — 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–14 lines × 2) crates/arroyo-connectors/src/filesystem/sink/two_phase_committer.rs:113— crates/arroyo-connectors/src/filesystem/sink/two_phase_committer.rs:113-126 | crates/arroyo-connectors/src/kafka/sink/mod.rs:381-393 — 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–14 lines × 2) crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs:488— crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs:488-498 | crates/arroyo-worker/src/arrow/tumbling_aggregating_window.rs:153-166 — before extracting anything, compare `crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs` and `crates/arroyo-worker/src/arrow/tumbling_aggregating_window.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 105 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 13) crates/arroyo-connectors/src/filesystem/delta.rs:111— crates/arroyo-connectors/src/filesystem/delta.rs:111-123 | crates/arroyo-connectors/src/filesystem/iceberg.rs:244-256 | crates/arroyo-connectors/src/filesystem/mod.rs:244-256 | crates/arroyo-connectors/src/fluvio/mod.rs:150-162 | crates/arroyo-connectors/src/kafka/mod.rs:226-238 | crates/arroyo-connectors/src/kinesis/mod.rs:108-120 | crates/arroyo-connectors/src/mqtt/mod.rs:183-195 | crates/arroyo-connectors/src/nats/mod.rs:266-278 | crates/arroyo-connectors/src/rabbitmq/mod.rs:200-212 | crates/arroyo-connectors/src/redis/mod.rs:416-428 | crates/arroyo-connectors/src/sse/mod.rs:103-115 | crates/arroyo-connectors/src/webhook/mod.rs:158-170 | crates/arroyo-connectors/src/websocket/mod.rs:245-257 — before extracting anything, compare `crates/arroyo-connectors/src/filesystem/delta.rs` and `crates/arroyo-connectors/src/filesystem/mod.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 3) crates/arroyo-connectors/src/polling_http/mod.rs:218— crates/arroyo-connectors/src/polling_http/mod.rs:218-230 | crates/arroyo-connectors/src/single_file/mod.rs:99-111 | crates/arroyo-connectors/src/stdout/mod.rs:102-114 — `crates/arroyo-connectors/src/single_file/mod.rs` and `crates/arroyo-connectors/src/stdout/mod.rs` 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 3 separate duplicated blocks between them, totalling at least 30 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.
Duplicated block (11–12 lines × 5) crates/arroyo-state/src/tables/table_manager.rs:417— crates/arroyo-state/src/tables/table_manager.rs:417-428 | crates/arroyo-state/src/tables/table_manager.rs:458-469 | crates/arroyo-state/src/tables/table_manager.rs:500-510 | crates/arroyo-state/src/tables/table_manager.rs:538-548 | crates/arroyo-state/src/tables/table_manager.rs:575-586 — 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 × 3) crates/arroyo-connectors/src/kafka/mod.rs:662— crates/arroyo-connectors/src/kafka/mod.rs:662-673 | crates/arroyo-connectors/src/kafka/mod.rs:687-698 | crates/arroyo-connectors/src/kafka/mod.rs:730-741 — 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 (11–12 lines × 2) crates/arroyo-worker/src/job_controller/controller.rs:377— crates/arroyo-worker/src/job_controller/controller.rs:377-387 | crates/arroyo-worker/src/job_controller/controller.rs:468-479 — 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–11 lines × 2) crates/arroyo-planner/src/extension/debezium.rs:55— crates/arroyo-planner/src/extension/debezium.rs:55-65 | crates/arroyo-planner/src/physical.rs:989-997 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 3) crates/arroyo-rpc/src/lib.rs:695— crates/arroyo-rpc/src/lib.rs:695-702 | crates/arroyo-rpc/src/lib.rs:741-748 | crates/arroyo-rpc/src/lib.rs:778-785 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (7–8 lines × 2) crates/arroyo-connectors/src/sse/operator.rs:105— crates/arroyo-connectors/src/sse/operator.rs:105-111 | crates/arroyo-connectors/src/websocket/operator.rs:89-96 — `crates/arroyo-connectors/src/sse/operator.rs` and `crates/arroyo-connectors/src/websocket/operator.rs` 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 3 separate duplicated blocks between them, totalling at least 41 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.
Duplicated block (7 lines × 16) crates/arroyo-connectors/src/filesystem/delta.rs:110— crates/arroyo-connectors/src/filesystem/delta.rs:110-116 | crates/arroyo-connectors/src/filesystem/iceberg.rs:243-249 | crates/arroyo-connectors/src/filesystem/mod.rs:243-249 | crates/arroyo-connectors/src/fluvio/mod.rs:149-155 | crates/arroyo-connectors/src/kafka/mod.rs:225-231 | crates/arroyo-connectors/src/kinesis/mod.rs:107-113 | crates/arroyo-connectors/src/mqtt/mod.rs:182-188 | crates/arroyo-connectors/src/nats/mod.rs:265-271 | crates/arroyo-connectors/src/polling_http/mod.rs:217-223 | crates/arroyo-connectors/src/rabbitmq/mod.rs:199-205 | crates/arroyo-connectors/src/redis/mod.rs:415-421 | crates/arroyo-connectors/src/single_file/mod.rs:98-104 | crates/arroyo-connectors/src/sse/mod.rs:102-108 | crates/arroyo-connectors/src/stdout/mod.rs:101-107 | crates/arroyo-connectors/src/webhook/mod.rs:157-163 | crates/arroyo-connectors/src/websocket/mod.rs:244-250 — before extracting anything, compare `crates/arroyo-connectors/src/filesystem/delta.rs` and `crates/arroyo-connectors/src/filesystem/mod.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 4) crates/arroyo-connectors/src/confluent/mod.rs:171— crates/arroyo-connectors/src/confluent/mod.rs:171-177 | crates/arroyo-connectors/src/kafka/mod.rs:357-363 | crates/arroyo-connectors/src/mqtt/mod.rs:258-264 | crates/arroyo-connectors/src/nats/mod.rs:293-299 — `crates/arroyo-connectors/src/confluent/mod.rs` and `crates/arroyo-connectors/src/kafka/mod.rs` 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 4 separate duplicated blocks between them, totalling at least 33 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.
Duplicated block (7 lines × 3) crates/arroyo-state/src/tables/table_manager.rs:437— crates/arroyo-state/src/tables/table_manager.rs:437-443 | crates/arroyo-state/src/tables/table_manager.rs:478-484 | crates/arroyo-state/src/tables/table_manager.rs:595-601 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 10) crates/arroyo-connectors/src/blackhole/mod.rs:63— crates/arroyo-connectors/src/blackhole/mod.rs:63-72 | crates/arroyo-connectors/src/filesystem/delta.rs:55-64 | crates/arroyo-connectors/src/filesystem/mod.rs:179-188 | crates/arroyo-connectors/src/fluvio/mod.rs:73-82 | crates/arroyo-connectors/src/impulse/mod.rs:84-93 | crates/arroyo-connectors/src/kinesis/mod.rs:61-70 | crates/arroyo-connectors/src/nexmark/mod.rs:142-151 | crates/arroyo-connectors/src/preview/mod.rs:55-64 | crates/arroyo-connectors/src/single_file/mod.rs:61-70 | crates/arroyo-connectors/src/stdout/mod.rs:60-69 — before extracting anything, compare `crates/arroyo-connectors/src/filesystem/delta.rs` and `crates/arroyo-connectors/src/filesystem/mod.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 4) crates/arroyo-connectors/src/fluvio/source.rs:55— crates/arroyo-connectors/src/fluvio/source.rs:55-64 | crates/arroyo-connectors/src/kinesis/source.rs:171-180 | crates/arroyo-connectors/src/rabbitmq/source.rs:49-58 | crates/arroyo-connectors/src/websocket/operator.rs:63-72 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
Duplicated block (12 lines × 4) crates/arroyo-connectors/src/fluvio/source.rs:209— crates/arroyo-connectors/src/fluvio/source.rs:209-221 | crates/arroyo-connectors/src/kafka/source/mod.rs:267-279 | crates/arroyo-connectors/src/kinesis/source.rs:398-410 | crates/arroyo-connectors/src/rabbitmq/source.rs:149-160 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
Duplicated block (10 lines × 5) crates/arroyo-connectors/src/kafka/mod.rs:213— crates/arroyo-connectors/src/kafka/mod.rs:213-222 | crates/arroyo-connectors/src/kinesis/mod.rs:95-104 | crates/arroyo-connectors/src/mqtt/mod.rs:170-179 | crates/arroyo-connectors/src/nats/mod.rs:252-262 | crates/arroyo-connectors/src/rabbitmq/mod.rs:186-196 — `crates/arroyo-connectors/src/kafka/mod.rs` and `crates/arroyo-connectors/src/kinesis/mod.rs` 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 8 separate duplicated blocks between them, totalling at least 76 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.
Duplicated block (9 lines × 6) crates/arroyo-connectors/src/fluvio/mod.rs:137— crates/arroyo-connectors/src/fluvio/mod.rs:137-146 | crates/arroyo-connectors/src/kafka/mod.rs:213-222 | crates/arroyo-connectors/src/kinesis/mod.rs:96-104 | crates/arroyo-connectors/src/mqtt/mod.rs:170-179 | crates/arroyo-connectors/src/nats/mod.rs:253-262 | crates/arroyo-connectors/src/rabbitmq/mod.rs:187-196 — `crates/arroyo-connectors/src/fluvio/mod.rs` and `crates/arroyo-connectors/src/kafka/mod.rs` 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 6 separate duplicated blocks between them, totalling at least 59 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.
Duplicated block (9 lines × 4) crates/arroyo-connectors/src/confluent/mod.rs:105— crates/arroyo-connectors/src/confluent/mod.rs:105-113 | crates/arroyo-connectors/src/kafka/mod.rs:182-190 | crates/arroyo-connectors/src/mqtt/mod.rs:139-147 | crates/arroyo-connectors/src/nats/mod.rs:157-165 — `crates/arroyo-connectors/src/confluent/mod.rs` and `crates/arroyo-connectors/src/kafka/mod.rs` 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 4 separate duplicated blocks between them, totalling at least 33 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.
Duplicated block (8 lines × 8) crates/arroyo-connectors/src/fluvio/mod.rs:139— crates/arroyo-connectors/src/fluvio/mod.rs:139-146 | crates/arroyo-connectors/src/kafka/mod.rs:215-222 | crates/arroyo-connectors/src/kinesis/mod.rs:97-104 | crates/arroyo-connectors/src/mqtt/mod.rs:172-179 | crates/arroyo-connectors/src/nats/mod.rs:255-262 | crates/arroyo-connectors/src/rabbitmq/mod.rs:189-196 | crates/arroyo-connectors/src/stdout/mod.rs:91-98 | crates/arroyo-connectors/src/webhook/mod.rs:147-154 — `crates/arroyo-connectors/src/fluvio/mod.rs` and `crates/arroyo-connectors/src/kafka/mod.rs` 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 6 separate duplicated blocks between them, totalling at least 59 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.
Duplicated block (8 lines × 4) crates/arroyo-connectors/src/filesystem/delta.rs:78— crates/arroyo-connectors/src/filesystem/delta.rs:78-85 | crates/arroyo-connectors/src/filesystem/mod.rs:205-212 | crates/arroyo-connectors/src/redis/mod.rs:398-405 | crates/arroyo-connectors/src/single_file/mod.rs:87-94 — before extracting anything, compare `crates/arroyo-connectors/src/filesystem/delta.rs` and `crates/arroyo-connectors/src/filesystem/mod.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 12) crates/arroyo-connectors/src/fluvio/mod.rs:146— crates/arroyo-connectors/src/fluvio/mod.rs:146-152 | crates/arroyo-connectors/src/kafka/mod.rs:222-228 | crates/arroyo-connectors/src/kinesis/mod.rs:104-110 | crates/arroyo-connectors/src/mqtt/mod.rs:179-185 | crates/arroyo-connectors/src/nats/mod.rs:262-268 | crates/arroyo-connectors/src/polling_http/mod.rs:214-220 | crates/arroyo-connectors/src/preview/mod.rs:87-93 | crates/arroyo-connectors/src/rabbitmq/mod.rs:196-202 | crates/arroyo-connectors/src/sse/mod.rs:99-105 | crates/arroyo-connectors/src/stdout/mod.rs:98-104 | crates/arroyo-connectors/src/webhook/mod.rs:154-160 | crates/arroyo-connectors/src/websocket/mod.rs:241-247 — `crates/arroyo-connectors/src/fluvio/mod.rs` and `crates/arroyo-connectors/src/kafka/mod.rs` 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 6 separate duplicated blocks between them, totalling at least 59 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.
Duplicated block (32 lines × 2 locations) webui/src/routes/connections/JsonForm.tsx:215— webui/src/routes/connections/JsonForm.tsx:215 · webui/src/routes/connections/JsonForm.tsx:358 — 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 (25 lines × 2 locations) webui/src/routes/connections/DefineSchema.tsx:212— webui/src/routes/connections/DefineSchema.tsx:212 · webui/src/routes/connections/DefineSchema.tsx:259 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (23 lines × 2 locations) webui/src/routes/connections/JsonForm.tsx:536— webui/src/routes/connections/JsonForm.tsx:536 · webui/src/routes/connections/JsonForm.tsx:686 — 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 (21 lines × 2 locations) webui/src/routes/connections/Connections.tsx:202— webui/src/routes/connections/Connections.tsx:202 · webui/src/routes/home/Home.tsx:121 — 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 (20 lines × 3 locations) webui/src/lib/util.ts:7— webui/src/lib/util.ts:7 · webui/src/lib/util.ts:32 · webui/src/lib/util.ts:57 — all 3 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) webui/src/routes/connections/JsonForm.tsx:497— webui/src/routes/connections/JsonForm.tsx:497 · webui/src/routes/connections/JsonForm.tsx:661 — 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 (18 lines × 2 locations) webui/src/routes/connections/ConnectionTester.tsx:205— webui/src/routes/connections/ConnectionTester.tsx:205 · webui/src/routes/connections/CreateProfile.tsx:134 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (17 lines × 2 locations) webui/src/routes/connections/CreateConnection.tsx:49— webui/src/routes/connections/CreateConnection.tsx:49 · webui/src/routes/connections/CreateConnection.tsx:81 — 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 (12 lines × 2 locations) webui/src/lib/data_fetching.ts:511— webui/src/lib/data_fetching.ts:511 · webui/src/lib/data_fetching.ts:591 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
R10 · Code Duplication· Duplicated block with local edits (11 matched lines × 2 locations) · ×1
Duplicated block with local edits (11 matched lines × 2 locations) webui/src/components/PipelinesTable.tsx:40— webui/src/components/PipelinesTable.tsx:40 · webui/src/routes/connections/Connections.tsx:108 — the two spans are one implementation copied and then locally edited — 75 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 (10 lines × 2 locations) webui/src/components/CreatePipelineTourModal.tsx:24— webui/src/components/CreatePipelineTourModal.tsx:24 · webui/src/components/TourCompleteModal.tsx:25 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (9 lines × 2 locations) webui/src/routes/connections/JsonForm.tsx:865— webui/src/routes/connections/JsonForm.tsx:865 · webui/src/routes/connections/JsonForm.tsx:914 — 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 (8 lines × 2 locations) webui/src/components/CheckpointDetails.tsx:78— webui/src/components/CheckpointDetails.tsx:78 · webui/src/components/CheckpointDetails.tsx:128 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (7 matched lines × 2 locations) · ×1
Duplicated block with local edits (7 matched lines × 2 locations) webui/src/components/PipelinesTable.tsx:45— webui/src/components/PipelinesTable.tsx:45 · webui/src/components/PipelinesTable.tsx:55 — the two spans are one implementation copied and then locally edited — 59 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (5 lines × 2 locations) webui/src/components/CheckpointDetails.tsx:42— webui/src/components/CheckpointDetails.tsx:42 · webui/src/components/PipelineRow.tsx:67 — 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.
Complex function CreatePipeline (cyclomatic 38, cognitive 44) webui/src/routes/pipelines/CreatePipeline.tsx:75— CreatePipeline has cyclomatic complexity 38 and cognitive complexity 44; 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 27, cognitive 34) webui/src/routes/connections/JsonForm.tsx:751— (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 PipelineDetails (cyclomatic 25, cognitive 29) webui/src/routes/pipelines/PipelineDetails.tsx:69— PipelineDetails has cyclomatic complexity 25 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function Checkpoints (cyclomatic 24, cognitive 27) webui/src/components/Checkpoints.tsx:91— Checkpoints has cyclomatic complexity 24 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function ConnectionTester (cyclomatic 22, cognitive 16) webui/src/routes/connections/ConnectionTester.tsx:36— ConnectionTester has cyclomatic complexity 22 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 SchemaFormatEditor (cyclomatic 17, cognitive 14) webui/src/routes/connections/DefineSchema.tsx:25— SchemaFormatEditor 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 (anonymous) (cyclomatic 16, cognitive 23) webui/src/components/CheckpointDetails.tsx:58— (anonymous) has cyclomatic complexity 16 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 ConfigEntry (cyclomatic 13, cognitive 14) webui/src/components/ConfigViewer.tsx:105— ConfigEntry has cyclomatic complexity 13 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 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 AutocompleteWidget (cyclomatic 12, cognitive 11) webui/src/routes/connections/JsonForm.tsx:230— AutocompleteWidget has cyclomatic complexity 12 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Dead file (~108 LoC) webui/src/lib/RadioGroup.tsx— no import path from any entry point (1 application, 2 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~47 LoC) webui/src/routes/pipelines/ResourcePanel.tsx— no import path from any entry point (1 application, 2 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Unused dependency '@chakra-ui/stepper' — Declared in webui/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 '@rjsf/chakra-ui' — Declared in webui/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 '@rjsf/validator-ajv8' — Declared in webui/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.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 32 significant file(s) lose their only recent owner: crates/arroyo-state-protocol/src/lib.rs, crates/arroyo-operator/src/operator.rs, crates/arroyo-connectors/src/filesystem/sink/v2/open_file.rs, crates/arroyo-worker/src/job_controller/controller.rs, crates/arroyo-connectors/src/filesystem/config.rs, crates/arroyo-state-protocol/src/workflow.rs, crates/arroyo-worker/src/network_manager.rs, crates/arroyo-connectors/src/filesystem/sink/iceberg/metadata.rs (+24 more). Pair on, review, or document these before any departure.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 1 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (34 single-owned of 232 analysed files in total, 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; 232 of the 302 production source files in this repository met that bar). They are anonymized user #2 (2 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above.
No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 1 of 26 project(s) overshoot their size bounds, lowering Project Cohesion to 9.2/10. The most over is `crates/arroyo-connectors` (22627 LoC, 168 public types across 29 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.
D34 · Knowledge Freshness· Further orphaned files (smaller) · ×1
Further orphaned files (smaller) — 17 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: crates/arroyo-connectors/src/nats/mod.rs, crates/arroyo-worker/src/arrow/instant_join.rs, crates/arroyo-connectors/src/rabbitmq/mod.rs, crates/arroyo-worker/src/arrow/window_fn.rs, crates/arroyo-planner/src/extension/debezium.rs, crates/arroyo-connectors/src/rabbitmq/source.rs, webui/src/routes/udfs/GlobalizeModal.tsx, webui/src/components/PipelinesTable.tsx (and 9 more) (19 orphaned of 232 analysed files in total, 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; 232 of the 302 production source files in this repository met that bar). 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.
D40 · Network Egress Confinement· No network policy · ×1
No network policy — No Kubernetes NetworkPolicy (or Cilium policy) found. Without one, every pod can talk to every other pod and reach out to the internet by default. Add a default-deny policy and open only the flows you need.
No seccomp profile — Workloads do not set a seccomp profile (RuntimeDefault or a Localhost profile). Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No AppArmor/SELinux confinement — Workloads declare no AppArmor or SELinux profile. A mandatory-access-control profile confines what a compromised container can touch on the host, complementing seccomp's syscall filter.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M2 · Architecture documentation· No architecture diagram/doc · ×1
No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
R7 · Dead Code· Unused export 'durationFormat' · ×1
Unused export 'durationFormat' webui/src/lib/util.ts:3— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'datarateFormat' · ×1
Unused export 'datarateFormat' webui/src/lib/util.ts:29— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'stringifyBigint' · ×1
Unused export 'stringifyBigint' webui/src/lib/util.ts:79— Nothing imports this binding — it is safe to review for removal.
Duplicated predicate webui/src/components/ConfigViewer.tsx:8— `value !== null && typeof value === 'object' && !Array.isArray(value)` appears character-identically in 2 files — webui/src/components/ConfigViewer.tsx, webui/src/routes/pipelines/PipelineConfigs.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.
Hand-rolled JSON/XML parsing via regex crates/arroyo-connectors/src/filesystem/sink/iceberg/mod.rs:92— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This Rust code already uses a real parser in the same package; use it here too.
Outdated: arc-swap — `arc-swap` is locked at 1.7.1 but 1.9.2 is the current stable release on crates.io, and it already satisfies the `"1.7.1"` requirement declared in crates/arroyo-rpc/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p arc-swap` and commit the updated REDACTED.
Outdated: async-compression — `async-compression` is locked at 0.4.19 but 0.4.49 is the current stable release on crates.io, and it already satisfies the `"0.4.3"` requirement declared in crates/arroyo-connectors/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p async-compression` and commit the updated REDACTED.
Outdated: async-ffi — `async-ffi` is locked at 0.5.0 but 0.5.1 is the current stable release on crates.io, and it already satisfies the `"0.5"` requirement declared in crates/arroyo-udf/arroyo-udf-host/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p async-ffi` and commit the updated REDACTED.
Outdated: aws-credential-types — `aws-credential-types` is locked at 1.2.11 but 1.3.0 is the current stable release on crates.io, and it already satisfies the `"1.2.0"` requirement declared in crates/arroyo-storage/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p aws-credential-types` and commit the updated REDACTED.
Outdated: aws-msk-iam-sasl-signer — `aws-msk-iam-sasl-signer` is locked at 1.0.0 but 1.0.1 is the current stable release on crates.io, and it already satisfies the `"1.0.0"` requirement declared in crates/arroyo-connectors/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p aws-msk-iam-sasl-signer` and commit the updated REDACTED.
Outdated: aws-sdk-kinesis — `aws-sdk-kinesis` is locked at 1.98.0 but 1.124.0 is the current stable release on crates.io, and it already satisfies the `"1.95"` requirement declared in crates/arroyo-connectors/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p aws-sdk-kinesis` and commit the updated REDACTED.
Outdated: clap — `clap` is locked at 4.5.39 but 4.6.7 is the current stable release on crates.io, and it already satisfies the `"4"` requirement declared in crates/arroyo/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p clap` and commit the updated REDACTED.
Outdated: futures-util — `futures-util` is locked at 0.3.31 but 0.3.34 is the current stable release on crates.io, and it already satisfies the `"0.3.28"` requirement declared in crates/arroyo-api/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p futures-util` and commit the updated REDACTED.
Outdated: glob — `glob` is locked at 0.3.2 but 0.3.4 is the current stable release on crates.io, and it already satisfies the `"0.3"` requirement declared in crates/arroyo-connectors/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p glob` and commit the updated REDACTED.
Outdated: integer-encoding — `integer-encoding` is locked at 4.0.2 but 4.1.0 is the current stable release on crates.io, and it already satisfies the `"4.0.2"` requirement declared in crates/arroyo-formats/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p integer-encoding` and commit the updated REDACTED.
Outdated: local-ip-address — `local-ip-address` is locked at 0.6.5 but 0.6.13 is the current stable release on crates.io, and it already satisfies the `"0.6"` requirement declared in crates/arroyo-rpc/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p local-ip-address` and commit the updated REDACTED.
Outdated: log — `log` is locked at 0.4.27 but 0.4.34 is the current stable release on crates.io, and it already satisfies the `"0.4.20"` requirement declared in crates/arroyo-rpc/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p log` and commit the updated REDACTED.
Outdated: memchr — `memchr` is locked at 2.7.4 but 2.8.3 is the current stable release on crates.io, and it already satisfies the `"2"` requirement declared in crates/arroyo-formats/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p memchr` and commit the updated REDACTED.
Outdated: percent-encoding — `percent-encoding` is locked at 2.3.1 but 2.3.2 is the current stable release on crates.io, and it already satisfies the `"2.3.1"` requirement declared in crates/arroyo-rpc/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p percent-encoding` and commit the updated REDACTED.
Outdated: postgres — `postgres` is locked at 0.19.10 but 0.19.14 is the current stable release on crates.io, and it already satisfies the `"0.19.5"` requirement declared in crates/arroyo-api/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p postgres` and commit the updated REDACTED.
Outdated: postgres-types — `postgres-types` is locked at 0.2.9 but 0.2.14 is the current stable release on crates.io, and it already satisfies the `"*"` requirement declared in crates/arroyo-api/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p postgres-types` and commit the updated REDACTED.
Outdated: proc-macro2 — `proc-macro2` is locked at 1.0.101 but 1.0.107 is the current stable release on crates.io, and it already satisfies the `"1.0"` requirement declared in crates/arroyo-udf/arroyo-udf-macros/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p proc-macro2` and commit the updated REDACTED.
Outdated: quote — `quote` is locked at 1.0.40 but 1.0.47 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in crates/arroyo-udf/arroyo-udf-host/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p quote` and commit the updated REDACTED.
Outdated: rust-embed — `rust-embed` is locked at 8.7.2 but 8.12.0 is the current stable release on crates.io, and it already satisfies the `"8"` requirement declared in crates/arroyo-api/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p rust-embed` and commit the updated REDACTED.
Outdated: rust_decimal — `rust_decimal` is locked at 1.37.2 but 1.43.0 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in crates/arroyo-connectors/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p rust_decimal` and commit the updated REDACTED.
Outdated: rustls-native-certs — `rustls-native-certs` is locked at 0.8.1 but 0.8.4 is the current stable release on crates.io, and it already satisfies the `"0.8"` requirement declared in crates/arroyo-connectors/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p rustls-native-certs` and commit the updated REDACTED.
Outdated: schemars — `schemars` is locked at 1.0.4 but 1.2.2 is the current stable release on crates.io, and it already satisfies the `"1.0.4"` requirement declared in crates/arroyo-connectors/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p schemars` and commit the updated REDACTED.
Outdated: smallvec — `smallvec` is locked at 1.15.1 but 1.16.2 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in crates/arroyo-rpc/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p smallvec` and commit the updated REDACTED.
Outdated: time — `time` is locked at 0.3.41 but 0.3.55 is the current stable release on crates.io, and it already satisfies the `"0.3"` requirement declared in crates/arroyo-api/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p time` and commit the updated REDACTED.
Outdated: tokio-postgres — `tokio-postgres` is locked at 0.7.13 but 0.7.18 is the current stable release on crates.io, and it already satisfies the `"*"` requirement declared in crates/arroyo-server-common/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p tokio-postgres` and commit the updated REDACTED.
+ 4 more in this group — see findings.md.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
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 — The repository ships application workloads but no cluster-governance resources (CRDs, admission webhooks, or a committed policy engine). Runtime threat-detection (Falco/Tetragon) and admission control (Kyverno/OPA-Gatekeeper/PodSecurity) are cluster-OPERATOR controls owned by the platform, not shipped by an application repo/chart — nothing for this repo to assess.
Run 01a0f0c8-5187-74fa-96da-4ab0a748fcf3 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 74 · Warnings: 505 · Recommendations: 26 · Info: 29 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 30-09-2026 @ 05: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.