quickwit — Watchdog Audit

Executive summary

⚠ 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 platform is a large, valuable asset currently rated at risk. With a score of 60%, the system is functional but carries significant exposure that threatens delivery speed and operational reliability. The sheer scale of the codebase means that technical debt here is not just a maintenance issue; it is a direct liability to the business, requiring immediate attention to prevent costly outages or security breaches.

The most critical vulnerability lies in security posture, which is the weakest lens for this substantial system. A score of 52% indicates that trust boundaries are not adequately enforced, leaving the organization exposed to potential data breaches and compliance failures. Given that rebuilding this asset would require nearly two person-years and significant capital, the cost of a security incident far outweighs the investment needed to harden the infrastructure. This is where remediation buys the most protection and reduces the highest business risk.

Another area of concern is production readiness, which sits at 67%. While the code itself is well-structured and the architecture is sound, the system lacks the robustness required for safe, continuous operation. This gap increases the likelihood of defects reaching production and complicates incident response. The absence of measured test coverage for key components further obscures the true stability of the application, making it difficult to predict how changes will impact performance or reliability.

Despite these risks, the foundation is strong. The code health and architecture scores are high, indicating that the logic is maintainable and changes do not ripple uncontrollably. The domain modeling is clear, and the event sourcing pattern is implemented perfectly, providing a solid base for future development. These strengths mean that once the immediate risks are addressed, the team can move quickly without fear of breaking the core system.

The highest-leverage action is to fix the Rust concurrency issues. Using blocking calls on async threads causes panics, which leads to immediate outages. Resolving this prevents crashes and stabilizes the runtime. This should be prioritized over the infrastructure findings, as it addresses a direct cause of instability. Addressing this single area will yield the most significant improvement in reliability with minimal effort, securing the platform’s operational integrity.

Code Health 88% ★ Exemplary Architecture 93% ★ Exemplary Maturity 78% Strong Readiness 67% Adequate · gated by P7 Security 52% Adequate · gated by D29, D30, D31, D36 Domain Modelling 86% ★ Exemplary Event Sourcing 100% ★ Exemplary Accessibility 71% Strong Performance 60% Adequate

How the score is built — each lens's share of the headline Width 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.

Security 52% · 45% weightPerformance 60% · 25% weightReadiness 67% · 14% weightAccessibility 71% · 8% weightMaturity 78% · 4% weightDomain Modelling 86% · 2% weightCode Health 88% · 1% weightArchitecture 93% · 1% weightEvent Sourcing 100% · 0% weight

Raise Security 52 → 70 (the Healthy floor) ⇒ headline 60 → ~66.

Code composition — where the lines go

Tests 100%

New since the last scan (52+)

52 finding(s) are new versus the previous scan (2026-09-12) — surfaced by this scheduled scan itself, no pull request required.

D1 · quickwit_search::leaf::normalize_timestamp_range (cyclomatic 18) quickwit/quickwit-search/src/leaf.rs
D2 · quickwit_search::leaf::normalize_timestamp_range (cognitive 25) quickwit/quickwit-search/src/leaf.rs
D2 · quickwit_control_plane::indexing_scheduler::scheduling::convert_physical_plan_to_solution (cognitive 21) quickwit/quickwit-control-plane/src/indexing_scheduler/scheduling/mod.rs
D2 · quickwit_control_plane::indexing_scheduler::scheduling::optimization::arrange_shards_in_home_zones (cognitive 18) quickwit/quickwit-control-plane/src/indexing_scheduler/scheduling/optimization.rs
D2 · quickwit_search::leaf::leaf_search_single_split (cognitive 16) quickwit/quickwit-search/src/leaf.rs
D3 · FileTooLong: indexing_scheduler/mod.rs quickwit/quickwit-control-plane/src/indexing_scheduler/mod.rs
D3 · FileTooLong: scheduling/mod.rs quickwit/quickwit-control-plane/src/indexing_scheduler/scheduling/mod.rs
D4 · Members sharing a duplicated core (4 members, 50+ identical tokens) quickwit/quickwit-proto/src/types/doc_mapping_uid.rs
D4 · Members sharing a duplicated core (4 members, 50+ identical tokens) quickwit/quickwit-serve/src/elasticsearch_api/model/error.rs
D4 · Duplicated block (19 lines × 2) quickwit/quickwit-indexing/src/actors/indexing_pipeline.rs
D4 · Duplicated block (8 lines × 2) quickwit/quickwit-query/src/query_ast/visitor.rs
D4 · Duplicated block (6 lines × 2) quickwit/quickwit-indexing/src/source/kafka_source.rs
D5 · Unstable project quickwit-compaction
D5 · Unstable project quickwit-control-plane
D5 · Unstable project quickwit-jaeger
D5 · Unstable project quickwit-janitor
D5 · Unstable project quickwit-lambda-client
D5 · Unstable project quickwit-lambda-server
D5 · Unstable project quickwit-rest-client
D5 · Unstable project quickwit-serve
D5 · Off the main sequence: quickwit-codegen
D5 · Off the main sequence: quickwit-datetime
D5 · Off the main sequence: quickwit-metrics
D5 · Off the main sequence: quickwit-config
D5 · Off the main sequence: quickwit-proto
D5 · Off the main sequence: quickwit-common
D8 · Coverage not measured — JavaScript/TypeScript suite
D15 · Hotspot: quickwit/quickwit-datetime/src/java_date_time_format.rs quickwit/quickwit-datetime/src/java_date_time_format.rs
D17 · TodoComment quickwit/quickwit-doc-mapper/src/tag_pruning.rs
D17 · TodoComment quickwit/quickwit-ingest/src/ingest_v2/routing_table.rs
D22 · Duplicate intent: `kill` and `quit` appear to perform the same action (terminating the actor) with identical signatures and return types. In actor models, 'kill' usually implies forceful termination while 'quit' might be graceful, but without distinct behavioral documentation or signature differences (e.g., returning a specific error for kill vs success for quit), they are confusingly redundant.
D22 · Duplicate intent: `ask` and `ask_for_res` have identical signatures. The suffix `_for_res` suggests a specific return type or behavior (perhaps returning a Result directly vs wrapping it), but the signature `Result` is generic enough to cover both. This creates ambiguity for the caller.
D22 · Duplicate intent: Same as above, `Mailbox` exposes both `ask` and `ask_for_res` with identical signatures. This inconsistency propagates from `ActorContext`.
D22 · Inconsistent naming and return types for observation: `ActorContext.observe` returns `ObservableState`, while `ActorHandle.observe` returns `Observation`. `Universe.observe` returns `ActorObservation`. These types likely contain overlapping data (state, type, etc.), but the naming (`observe` vs `observe` vs `observe`) and return types vary by context, making it unclear which method to use for a given level of detail.
D22 · Duplicate intent: `search_index` and `search_index_cli` have identical signatures and likely perform the same CLI execution logic. The `_cli` suffix is redundant if both are in the CLI module.
D29 · REDACTED
D30 · REDACTED
D30 · REDACTED
D30 · REDACTED
D30 · REDACTED
D30 · REDACTED
R10 · Duplicated block (17 lines × 2 locations) quickwit/quickwit-ui/src/components/TimeRangeSelect.tsx
R10 · Duplicated block (13 lines × 2 locations) quickwit/quickwit-ui/src/components/QueryEditor/AggregationEditor.tsx
R10 · Duplicated block (10 lines × 2 locations) quickwit/quickwit-ui/src/components/SideBar.tsx
R10 · Duplicated block (10 lines × 2 locations) quickwit/quickwit-ui/src/views/NodeInfoView.tsx
P7 · Outbound HTTP without resilience quickwit/quickwit-indexing/src/source/pulsar_source.rs
AC3 · <html> without a lang REDACTED
AC3 · Document without a <title> REDACTED
PF3 · Sync-over-async blocking quickwit/quickwit-metastore/src/metastore/mod.rs
PF3 · Sync-over-async blocking quickwit/quickwit-metastore/src/metastore/mod.rs
PF3 · Sync-over-async blocking quickwit/quickwit-metastore/src/metastore/mod.rs
PF3 · Sync-over-async blocking quickwit/quickwit-metastore/src/metastore/mod.rs

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.

Rebuild cost & value ~ Modeled — €86,000–€430,000

Cost to rebuild	€86,000–€430,000 (0.9–2.7 person-years (1,440–4,567 h), ~1–4 engineers)
Domain complexity	Standard — harder problems cost more per line
Quality factor	0.8× (at 60% quality) — the last 20% of quality is most of the work
Size & shape	Large · effort split not classified (source measured from disk; the effort-tier breakdown is a C#-only syntax walk)

This codebase represents roughly ~1.8 person-years of build effort (about ~€260,000 to rebuild). Its weakest lens is Security at 52% — 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.8× 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.

Rust: `.await` the future instead of `block_on` (on a Tokio runtime thread it panics outright) and use `tokio::time::sleep(..).await` instead of `std::thread::sleep`; where synchronous code must run, move it to `tokio::task::spawn_blocking` or `block_in_place`.

+3.3 pts · Medium effort · Async & latency hygiene

Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing.

+1.6 pts · Low effort · Supply-chain Provenance & Signing

Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing.

+1.6 pts · Low effort · Supply-chain Provenance & Signing

Diagnosis — what's actually going on

Value concentrated against a weak lens · Medium · Value at risk

This is a Large asset (~1.8 person-years to rebuild), and its weakest lens is Security at 52%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.

Evidence: valuation: Large, ~1.8 person-years rebuild (222,917 LoC) · weakest lens: Security 52%

→ Direct remediation budget at Security 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: Rust: `.await` the future instead of `block_on` (on a Tokio runtime thread it panics outright) and use `tokio::time::sleep(..).await` instead of `std::thread::sleep`; where synchronous code must run, move it to `tokio::task::spawn_blocking` or `block_in_place`. The rest can wait behind it.

Evidence: priority ranking: top of 5 ranked by impact/effort

→ Rust: `.await` the future instead of `block_on` (on a Tokio runtime thread it panics outright) and use `tokio::time::sleep(..).await` instead of `std::thread::sleep`; where synchronous code must run, move it to `tokio::task::spawn_blocking` or `block_in_place`.

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

640 modules, 1942 dependencies. 11 dependency cycles across 132 modules, marked above the diagonal.

Showing the 40 most-connected modules; 600 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.
depends on →	1 quickwit_actors.channel_with_priority	2 quickwit_common.pubsub	3 quickwit_common.uri	4 quickwit_ingest.notifications	5 quickwit_metrics.gauge	6 quickwit_proto.types.index_uid	7 quickwit_proto.types.shard_id	8 quickwit_query.elastic_query_dsl	9 quickwit_rest_client.error	10 quickwit_actors.mailbox	11 quickwit_common.tower.metrics	12 quickwit_config.index_config	13 quickwit_metastore.checkpoint	14 quickwit_metastore.split_metadata	15 quickwit_proto.types	16 quickwit_query.query_ast	17 quickwit_storage.storage_resolver	18 quickwit_actors.actor_context	19 quickwit_cluster.cluster	20 quickwit_doc_mapper.doc_mapper.doc_mapper_impl	21 quickwit_ingest.codegen.ingest_service	22 quickwit_proto.codegen.quickwit.quickwit.ingest	23 quickwit_proto.indexing	24 quickwit_actors.actor	25 quickwit_config.node_config	26 quickwit_proto.codegen.quickwit.quickwit.ingest.ingester	27 quickwit_proto.codegen.quickwit.quickwit.metastore	28 quickwit_config.source_config	30 quickwit_proto.codegen.quickwit.quickwit.ingest.router	31 quickwit_search.service	33 quickwit_indexing.source	34 quickwit_opentelemetry.otlp.traces	35 quickwit_search.root	39 quickwit_proto.codegen.quickwit.quickwit.search
1 quickwit_actors.channel_with_priority
2 quickwit_common.pubsub
3 quickwit_common.uri
4 quickwit_ingest.notifications
5 quickwit_metrics.gauge
6 quickwit_proto.types.index_uid
7 quickwit_proto.types.shard_id
8 quickwit_query.elastic_query_dsl
9 quickwit_rest_client.error
10 quickwit_actors.mailbox	3				1
11 quickwit_common.tower.metrics					3
12 quickwit_config.index_config			1
13 quickwit_metastore.checkpoint				4
14 quickwit_metastore.split_metadata						1																					1
15 quickwit_proto.types						2	1
16 quickwit_query.query_ast								1
17 quickwit_storage.storage_resolver			1
18 quickwit_actors.actor_context	2								1	2														2
19 quickwit_cluster.cluster							1								1
20 quickwit_doc_mapper.doc_mapper.doc_mapper_impl																1
21 quickwit_ingest.codegen.ingest_service	1									4	3
22 quickwit_proto.codegen.quickwit.quickwit.ingest				2		4	4								1
23 quickwit_proto.indexing		1				2					1				3
24 quickwit_actors.actor	2								1									3
25 quickwit_config.node_config			1												1								1
26 quickwit_proto.codegen.quickwit.quickwit.ingest.ingester	1			5		10	7			4	7											8
27 quickwit_proto.codegen.quickwit.quickwit.metastore	1	5	5			30	4			4	33	5		1								3						2
28 quickwit_config.source_config			1																								2
29 quickwit_control_plane.control_plane	1	1	1							1					2			1					2	3			10
30 quickwit_proto.codegen.quickwit.quickwit.ingest.router	1			1		1	1			4	1											2				1
31 quickwit_search.service																	1								1		1							25
32 quickwit_indexing.actors.indexing_service		1								3		1		1	1		1	1	1				3	2	1		1	1
33 quickwit_indexing.source		1			1	1				2		1	3		1		2						1	4			2	2
34 quickwit_opentelemetry.otlp.traces		1	1																		1	2							1
35 quickwit_search.root			1			2								2		2											1			1				11
36 quickwit_indexing.actors.indexer	1				1					1		2	1					2		1			3	3			2					1
37 quickwit_indexing.actors.indexing_pipeline		1			1					2		2					1	1		1			1	3			1	1			1
38 quickwit_indexing.actors.uploader	1	1				1				1		2	1	1				3						2			2					1
39 quickwit_proto.codegen.quickwit.quickwit.search		1																									1						2
40 quickwit_serve	2	2	1							2					1		1		2		1				3	3	2		1	1		1

Dependency, pointing down the layeringAbove the diagonal — part of a cycleThe module itself

At a glance — Code Health · 88% · Exemplary ·

The Good

D1 · Rust Cyclomatic Complexity 7.1 D3 · Rust God Classes 9.0 D4 · Rust Code Duplication 9.8 D17 · Rust Explicit Debt 9.8 R1 · React / TS Type Safety 7.8 R10 · React / TS Code Duplication 9.5 R2 · React / TS Cyclomatic Complexity 10.0 R3 · React / TS Large Files 10.0 R7 · React / TS Dead Code 9.2

The Bad

D2 · Rust Cognitive Complexity 6.6

At a glance — Architecture · 93% · Exemplary ·

The Good

D26 · Rust Project Cohesion 7.7 D35 · Rust Change Coupling 9.8 AX10 · Repo Code composition 10.0 AX3 · Repo Project dependency cycles 10.0 AX4 · Repo Dependency direction 10.0 AX9 · Repo CQS / query purity 10.0 R9 · React / TS Circular Imports 10.0

The Bad

D5 · Rust Coupling 6.6 D22 · Rust Internal API Consistency 6.0

At a glance — Maturity · 78% · Strong ·

The Good

D15 · Rust Churn × Complexity Hotspots 9.8 D16 · Rust Bus Factor 9.5 D19 · Rust Documentation Quality 9.0 D21 · Rust Naming Consistency 10.0 D34 · Rust Knowledge Freshness 9.5 M1 · Repo Documentation (README) 8.0 M3 · Repo Folder & project structure 10.0 M4 · Repo Documentation accuracy 10.0

The Bad

M2 · Repo Architecture documentation 5.0

The Ugly

D20 · Rust ADR Quality 0.0

At a glance — Readiness · 67% · Adequate · gated by P7 ·

The Good

D9 · Rust Test Distribution 10.0 D10 · Rust Test Quality 10.0 D12 · Rust Dependency Hygiene 7.9 D13 · Rust Secret Scanning 10.0 D14 · Rust License Compliance 10.0 P1 · Repo CI/CD gates 10.0 P2 · Repo Observability 9.8 P3 · Repo Security & performance tooling 8.0 P4 · Repo Deployment & Rollback 10.0 P5 · Repo DR & Backup 7.0 P6 · Repo Release Hygiene 10.0 P8 · Repo Schema migrations 10.0 R4 · React / TS Test Coverage 9.1 R6 · React / TS Tooling 10.0 R8 · React / TS Dependency Hygiene 6.5

The Ugly

P7 · Repo Outbound HTTP resilience 3.0

At a glance — Security · 52% · Adequate · gated by D29, D30, D31, D36 ·

The Good

D28 · Rust Secrets (history) 10.0 D37 · Rust Vulnerability-disclosure Policy 10.0 D43 · Rust Malicious Dependencies 10.0

The Ugly

D29 · Rust Static Analysis (SAST) 0.1 D30 · Rust Dependency Vulnerabilities 1.4 D31 · Rust IaC & Container Security 2.4 D36 · Rust Supply-chain Provenance & Signing 2.5

At a glance — Domain Modelling · 86% · Exemplary ·

The Good

DM4 · Repo Rich vs anemic domain model 10.0 DM5 · Repo Encapsulated state 6.8 DM6 · Repo Domain ↔ infrastructure boundary 10.0

At a glance — Event Sourcing · 100% · Exemplary ·

The Good

ES1 · Repo Fold determinism 10.0 ES2 · Repo Immutable events 10.0

At a glance — Accessibility · 71% · Strong ·

The Good

AC1 · Repo Text alternatives 10.0 AC2 · Repo Forms & labels 7.8 AC3 · Repo Page structure 7.7 AC6 · Repo Visual & motion safety 10.0

The Ugly

AC7 · Repo A11y enforcement 4.0

At a glance — Performance · 60% · Adequate ·

The Bad

PF3 · Repo Async & latency hygiene 6.0

Security & Compliance — OWASP Top-10 mapping

Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).

OWASP category	Findings	Severity
A03:2021 — Injection	36	High / Critical
A05:2021 — Security Misconfiguration	32	High / Critical
A06:2021 — Vulnerable & Outdated Components	28	High / Critical

Roadmap

First, address async and latency hygiene by ensuring all futures are properly awaited and synchronous work is offloaded to blocking tasks to prevent runtime panics. Next, resolve the seventeen high-severity infrastructure-as-code and container security findings, prioritizing issues in Dockerfiles and S3 configurations. Then, remediate the twelve medium-severity IaC and container security issues, focusing on RDS and cluster definitions. Finally, establish supply-chain integrity by generating a Software Bill of Materials and implementing artifact signing.

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

Do this	Helps	Effort	Dimension
Rust: `.await` the future instead of `block_on` (on a Tokio runtime thread it panics outright) and use `tokio::time::sleep(..).await` instead of `std::thread::sleep`; where synchronous code must run, move it to `tokio::task::spawn_blocking` or `block_in_place`.	+3.3 pts	Medium	Async & latency hygiene
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing.	+1.6 pts	Low	Supply-chain Provenance & Signing
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing.	+1.6 pts	Low	Supply-chain Provenance & Signing
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing.	+1.6 pts	Low	Supply-chain Provenance & Signing
Resolve the 8 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (7), REDACTED.	+1.6 pts	Low	Dependency Vulnerabilities
Resolve the 7 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (7).	+1.4 pts	Low	Dependency Vulnerabilities
Resolve the 17 High IaC finding(s) in IaC & Container Security — start with REDACTED (7), REDACTED (5), REDACTED (2).	+2.6 pts	Medium	IaC & Container Security
Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED.	+1.3 pts	Low	Static Analysis (SAST)

File quality

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

File	Score	Band	Worst signal
REDACTED	1.4	Slop	IaC & Container Security: High IaC: REDACTED
REDACTED	1.6	Slop	Dependency Vulnerabilities: High CVE: REDACTED
REDACTED	2.1	Slop	Static Analysis (SAST): High: REDACTED
REDACTED	2.3	Slop	Static Analysis (SAST): High: REDACTED
REDACTED	3.0	Mixed	Dependency Vulnerabilities: High CVE: REDACTED
REDACTED	3.7	Mixed	IaC & Container Security: Critical IaC: REDACTED
REDACTED	4.4	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	4.8	Mixed	IaC & Container Security: High IaC: REDACTED
REDACTED	5.1	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	5.1	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	5.1	Mixed	IaC & Container Security: High IaC: REDACTED
REDACTED	5.8	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	5.8	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	5.8	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	5.8	Mixed	IaC & Container Security: High IaC: REDACTED
REDACTED	5.8	Mixed	IaC & Container Security: High IaC: REDACTED
quickwit/quickwit-storage/src/object_storage/azure_blob_storage.rs	5.9	Mixed	Code Duplication: Duplicated block (34 lines × 2)
quickwit/quickwit-search/src/collector.rs	6.0	Mixed	Explicit Debt: TodoComment
quickwit/quickwit-serve/src/lib.rs	6.0	Mixed	Explicit Debt: TodoComment
quickwit/quickwit-query/src/query_ast/tantivy_query_ast.rs	6.0	Mixed	Explicit Debt: TodoComment

How the grades work

Every finding carries one of four grades. Three say how serious it is. The fourth says this survey could not settle it — and it is a grade, not a gap.

Critical — 62

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

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

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

Could not be resolved — 48

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. 58 of 63 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 — 63 dimensions across the health lenses

D1D2D3D4D5D9D10D12D13D14D15D16D17D19D20D21D22D26D28D29D30D31D34D35D36D37D43AC1AC2AC3AC6AC7AX10AX3AX4AX9DM4DM5DM6ES1ES2M1M2M3M4P1P2P3P4P5P6P7P8PF3R1R10R2R3R4R6R7R8R9

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, 588 of 627 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	5.3.0	✓ deterministic
Native secret scanner	Hardcoded secrets / credentials	1.0.0	✓ deterministic
Watchdog duplication detector (in-process)	Code duplication	1.0.0	✓ deterministic
Coverage (coverlet / dotnet-coverage)	Line & branch coverage	10.0.400	✓ deterministic
NuGet / dotnet	Outdated, vulnerable & deprecated dependencies	10.0.400	✓ deterministic
git / LibGit2Sharp	Churn hotspots, knowledge concentration, history	2.43.0 · 0.31.0	✓ deterministic
gitleaks · semgrep · trivy · checkov	Secrets in history, SAST, CVEs, IaC & container, PII / GDPR	1.86.0 · 0.69.3 · 3.2.533	✓ deterministic
LLM (sampled · advisory)	Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement	Local LLM	◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a0eaf6-5b61-7fe4-aed8-2a512c367cf6.

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

Run transparency — what happened this run

What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.

D6 Cohesion (LCOM4) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
D10 Test Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 10 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 54 test source file(s) (.rs) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
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 reliability NOT SCORED: this repository's production source includes .rs, and the built-in reliability runner cannot re-run the .rs test suite(s) — so reliability was not measured for the repository as a whole. The JavaScript/TypeScript (jest via `yarn install --frozen-lockfile --ignore-scripts` in quickwit/quickwit-ui/ (7 tests)): measured (0 flaky) suite(s) did re-run, and came back with 0 flaky across 1 measured tier(s) — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — test reliability is excluded from the score rather than counted.
D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `quickwit/quickwit-ui/vite.config.ts` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
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.
AX1 Captive dependencies — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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.
AX2 Stateful singletons — 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.
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.
DM3 Integration-event coupling — 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. Not scored — a domain type leaking across a crate boundary cannot be told apart from source alone from a legitimate shared-kernel crate. Reported as guidance rather than measured.
DM7 Repository granularity — 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. Not scored — detecting 'a repository per CHILD entity' needs the aggregate-root structure, which is not resolvable from source alone here. Reported as guidance rather than measured.
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.
P10 Library API & versioning — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads NuGet packaging and C# public API only, and no .NET project was loaded for this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
PF1 Benchmark discipline — 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.
PF2 Allocation hygiene — 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.
X10 Duplicated predicate — 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.
X29 Per-element action decided by a fixed element — 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.
X32 Type resolved by simple name across every loaded assembly — 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.
X6 Hand-rolled structured-format parsing — 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.
X7 Silent fallback defaults — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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: 1 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.

Limitations & what we did not check

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.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
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").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality 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.
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.
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.
DM4 Rich vs anemic domain model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of 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".
P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

The LLM boundary

LLM-set scores this run (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.

Dimensions

D1 · Cyclomatic Complexity7.1 / 10Strong✓ Tool-verified

What it measures: How tangled the control flow is — methods with many branches are hard to test and change.

Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.

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

20 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was SortingFieldExtractorComponent::convert_to_u64_ff_val at 50. A further 4 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 quickwit_metastore_utils::bin::replay::replay_grpc_request at 18 — they are counted neither in the figure above nor in this dimension's score. 4 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: quickwit/quickwit-metastore-utils/src/bin/replay.rs (quickwit_metastore_utils::bin::replay::replay_grpc_request at 18), quickwit/quickwit-common/src/tower/metrics.rs (quickwit_common::tower::metrics::grpc_code_label at 17), quickwit/quickwit-query/src/elastic_query_dsl/mod.rs (ElasticQueryDslInner::convert_to_query_ast at 17), quickwit/quickwit-doc-mapper/src/tag_pruning.rs (quickwit_doc_mapper::tag_pruning::extract_unsimplified_tags_filter_ast at 16). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.

quickwit_serve::serve_quickwit (cyclomatic 32) · ×3quickwit/quickwit-serve/src/lib.rs:569

quickwit_metastore::metastore::file_backed::file_backed_index::split_query_predicate (cyclomatic 23) · ×2quickwit/quickwit-metastore/src/metastore/file_backed/file_backed_index/mod.rs:724

SortingFieldExtractorComponent::convert_to_u64_ff_val (cyclomatic 50)quickwit/quickwit-search/src/collector.rs:214

TantivyBoolQuery::simplify (cyclomatic 30)quickwit/quickwit-query/src/query_ast/tantivy_query_ast.rs:179

quickwit_ingest::ingest_v2::router::update_ingest_metrics (cyclomatic 22)quickwit/quickwit-ingest/src/ingest_v2/router.rs:507

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

What to do

Resolve the 3 quickwit_serve finding(s) in Cyclomatic Complexity — start with lib.rs, grpc.rs, rest.rs. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 2 quickwit_metastore finding(s) in Cyclomatic Complexity — start with mod.rs, utils.rs. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 SortingFieldExtractorComponent finding(s) in Cyclomatic Complexity — start with collector.rs. — One of this dimension's main actionable groups (1 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.

Do you agree with this assessment?

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

What it measures: How hard the code is for a person to follow, beyond raw branching.

Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.

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

58 method(s) exceeded the cognitive complexity threshold of 15; the worst was SortingFieldExtractorComponent::convert_to_u64_ff_val at 56.

quickwit_control_plane::indexing_scheduler::scheduling::convert_scheduling_solution_to_physical_plan (cognitive 32) · ×7quickwit/quickwit-control-plane/src/indexing_scheduler/scheduling/mod.rs:393

quickwit_serve::serve_quickwit (cognitive 52) · ×5quickwit/quickwit-serve/src/lib.rs:569

quickwit_search::leaf::run_offloaded_search_tasks (cognitive 27) · ×4quickwit/quickwit-search/src/leaf.rs:1770

DocMapper::doc_to_json (cognitive 29) · ×3quickwit/quickwit-doc-mapper/src/doc_mapper/doc_mapper_impl.rs:574

quickwit_doc_mapper::doc_mapper::mapping_tree::extract_json_val (cognitive 24) · ×3quickwit/quickwit-doc-mapper/src/doc_mapper/mapping_tree.rs:449

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

What to do

Resolve the 7 quickwit_control_plane finding(s) in Cognitive Complexity — start with mod.rs (5), scheduling_logic.rs, optimization.rs. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 5 quickwit_serve finding(s) in Cognitive Complexity — start with lib.rs, grpc.rs, rest_handler.rs. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 4 quickwit_search finding(s) in Cognitive Complexity — start with leaf.rs (3), root.rs. — One of this dimension's main actionable groups (4 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 Classes9.0 / 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.

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

65 god class(es) detected.

FileTooLong: postgres/metastore.rs · ×29quickwit/quickwit-metastore/src/metastore/postgres/metastore.rs

FunctionTooLong: quickwit_serve::serve_quickwit · ×14quickwit/quickwit-serve/src/lib.rs:569

MethodTooLong: Ingester.persist_inner · ×10quickwit/quickwit-ingest/src/ingest_v2/ingester.rs:387

ClassTooLong: PostgresqlMetastore · ×8quickwit/quickwit-metastore/src/metastore/postgres/metastore.rs:91

TooManyMethods: ControlPlaneModel · ×3quickwit/quickwit-control-plane/src/model/mod.rs:54

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

What to do

Resolve the 29 FileTooLong finding(s) in God Classes — start with mod.rs (6), lib.rs (2), metastore.rs. — One of this dimension's main actionable groups (29 warning-level).
Resolve the 14 FunctionTooLong finding(s) in God Classes — start with lib.rs (2), AggregationEditor.tsx, grpc.rs. — One of this dimension's main actionable groups (14 warning-level).
Resolve the 10 MethodTooLong finding(s) in God Classes — start with ingester.rs, metastore.rs, range_query.rs. — One of this dimension's main actionable groups (10 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.

Do you agree with this assessment?

D4 · Code Duplication9.8 / 10Stronggated by 82 serious findings✓ Tool-verified

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

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

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

80 duplicated block group(s) detected. A further 2 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.

Duplicated block (8 lines × 2) · ×9quickwit/quickwit-cli/src/index.rs:434

Duplicated block (9 lines × 2) · ×8quickwit/quickwit-config/src/metastore_config.rs:59

Duplicated block (7 lines × 2) · ×7quickwit/quickwit-rest-client/src/rest_client.rs:641

Duplicated block (6 lines × 2) · ×7quickwit/quickwit-cli/src/source.rs:379

Duplicated block (5 lines × 2) · ×7quickwit/quickwit-metrics/src/counter.rs:204

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

What to do

Resolve the 9 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with index.rs, source.rs, logs.rs. — One of this dimension's main actionable groups (9 warning-level).
Resolve the 8 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with logs.rs (2), metastore_config.rs, ingester.rs. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 7 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with jemalloc.rs (2), rest_client.rs, decompression.rs. — One of this dimension's main actionable groups (7 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 · Coupling6.6 / 10Adequate✓ Tool-verified

What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.

Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.

Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.

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

35 production modules (Cargo+npm), 0 dependency cycle(s), 8 unstable depended-on module(s). Read from the build's own module declarations; 6 module(s) off the main sequence, with abstractness counted on 33 of the 35 (the rest declare no modelled class or interface, export only macros, or are not Gradle/Maven modules or Cargo crates).

Off the main sequence: quickwit-codegen · ×6

Unstable project quickwit-compaction

Unstable project quickwit-control-plane

Unstable project quickwit-jaeger

Unstable project quickwit-janitor

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

What to do

Resolve the 6 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 1 Unstable project quickwit-compaction finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Unstable project quickwit-control-plane 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.

Do you agree with this assessment?

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.

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

2453 test methods: 2359 unit, 91 integration, 0 BDD, 3 e2e. The JavaScript/TypeScript suite contributes 10 `it`/`test` case(s) across 8 test file(s) declaring at least one; its tier split is read from package names and paths only. The Rust suite contributes 2443 `#[test]` function(s) across 383 file(s) declaring at least one; its unit/integration split is Cargo's own — 7 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.

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

Do you agree with this assessment?

D10 · Test Quality10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the tests truly assert behaviour rather than just running the code.

Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.

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

0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 10 tests. Measured on the JavaScript/TypeScript suite only — at least 54 test source file(s) (.rs) went unread, so its test quality is unmeasured and is not in these counts.

✓ On the Gold path — maintain.

Detailed fixes: d10_recommendation.md.

Do you agree with this assessment?

D12 · Dependency Hygiene~~9.9~~ 7.9 / 10Strong✓ Tool-verified

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

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

Maturity: Documented → Verified → Prevented · effective 7.9 / 10 · rule-coverage 80% · ceiling Verified

2 outdated, 0 yanked direct Cargo dependencies. 4 of 5 direct crates were graded against crates.io (0 not published there, 1 not resolved by a committed REDACTED). 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: glob · ×2

What to do

Maintain Dependency Hygiene — already on the Gold path. — No findings, and enforcement is at this dimension's ceiling.

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

Do you agree with this assessment?

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

What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.

Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.

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

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

Do you agree with this assessment?

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

What it measures: Whether the licenses of third-party packages are compatible with your policy.

Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.

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

0 of 1000 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. A further 16 crate(s) in the closure resolve from git, a path or a private registry and publish no licence this pass can read; they are outside this verdict. This repository publishes itself under Apache-2.0, which is its own choice and is not judged here.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

Do you agree with this assessment?

D15 · Churn × Complexity Hotspots9.8 / 10Stronggated by 6 serious findings✓ Tool-verified

What it measures: Files that change often and are also complex — the riskiest hotspots.

Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.

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

Top hotspots: quickwit/quickwit-serve/src/lib.rs (17×32=544); quickwit/quickwit-ingest/src/ingest_v2/ingester.rs (11×20=220); quickwit/quickwit-metastore/src/metastore/postgres/utils.rs (5×20=100)

Hotspot: quickwit/quickwit-serve/src/lib.rs · ×6quickwit/quickwit-serve/src/lib.rs:569

What to do

Resolve the 6 Hotspot finding(s) in Churn × Complexity Hotspots — start with lib.rs, ingester.rs, utils.rs. — One of this dimension's main actionable groups (6 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 Factor9.5 / 10Exemplary✓ 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.

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

23 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is quickwit/quickwit-metrics/src/lib.rs. Counted over 505 of the 621 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 · ×3

Further sole-owners (lower concentration)

✓ On the Gold path — maintain.

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

Do you agree with this assessment?

D17 · Explicit Debt9.8 / 10Stronggated by 214 serious findings✓ Tool-verified

What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.

Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.

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

214 deducted task-comment markers across 222917 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.

TodoComment · ×206quickwit/quickwit-actors/src/spawn_builder.rs:405

FixmeComment · ×7quickwit/quickwit-control-plane/src/indexing_scheduler/mod.rs:308

HackCommentquickwit/quickwit-storage/src/cache/quickwit_cache.rs:112

What to do

Resolve the 206 TodoComment finding(s) in Explicit Debt — start with mod.rs (15), control_plane.rs (9), gcp_pubsub_source.rs (8). — One of this dimension's main actionable groups (206 warning-level).
Resolve the 7 FixmeComment finding(s) in Explicit Debt — start with mod.rs (2), metastore.rs (2), s3_compatible_storage.rs (2). — One of this dimension's main actionable groups (7 warning-level).
Resolve the 1 HackComment finding(s) in Explicit Debt — start with quickwit_cache.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.

Do you agree with this assessment?

D19 · Documentation QualityExemplary◐ Sampled · advisory

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.

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

The repository's root README gives a strong overview (it is the first document and describes Quickwit as 'the fastest search engine on cloud storage' for observability use cases) plus links to docs, downloads, and community channels. The distribution/ecs/README and quickwit-actors/README each show deployment/configure content with code blocks, while the root README omits installation/build guidance (which is where it belongs). All 23 README files are present and well structured around a documented project; the quality sits at 9 because the only missing element across all documents is an overall repository-level overview/installation/usage/contribution section for the root, which is not clipped. The repository is well documented with a README for each directory (e.g. quickwit-serve, quickwit-ui, rest-api-tests) that describes what the directory contains and how to use it, plus an architecture/Docs markdown collection of 71 files covering design decisions, API patterns, migration docs, and index configuration. The root-level documentation is sparse but strong: the main index-config document gives a complete YAML format description plus every retention policy setting (period/scalar, scoping), while the overview for each directory is clear.

Documentation: contradicts the codequickwit/quickwit-metastore/migrations/postgresql_deferred/README.md

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.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.

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

No architecture decision records were found.

No ADRs found

What to do

Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).

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

Do you agree with this assessment?

D21 · Naming ConsistencyExemplary◐ Sampled · 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.

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

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 ConsistencyAdequate◐ 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.

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

5 API inconsistencies across a 400-member sample of 692 exposed types.

Duplicate intent: `kill` and `quit` appear to perform the same action (terminating the actor) with identical signatures and return types. In actor models, 'kill' usually implies forceful termination while 'quit' might be graceful, but without distinct behavioral documentation or signature differences (e.g., returning a specific error for kill vs success for quit), they are confusingly redundant. · ×4

Inconsistent naming and return types for observation: `ActorContext.observe` returns `ObservableState`, while `ActorHandle.observe` returns `Observation`. `Universe.observe` returns `ActorObservation`. These types likely contain overlapping data (state, type, etc.), but the naming (`observe` vs `observe` vs `observe`) and return types vary by context, making it unclear which method to use for a given level of detail.

What to do

Resolve the 4 Duplicate intent finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 1 Inconsistent naming and return types for observation 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.

Do you agree with this assessment?

D26 · Project Cohesion7.7 / 10Strong✓ Tool-verified

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

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

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

4 of 34 build units (Cargo) flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesion

What to do

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

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

Do you agree with this assessment?

D28 · Secrets (history)10.0 / 10Exemplary○ Nothing flagged

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.

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

gitleaks scanned the full history AND the current working tree and found no secrets.

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

Do you agree with this assessment?

D29 · Static Analysis (SAST)0.1 / 10Critical✓ Tool-verified

What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.

Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.

Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).

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

36 finding(s): 0 critical, 28 high, 8 medium, 0 low. semgrep hit a parse error in 8 file(s) — `quickwit/quickwit-doc-mapper/benches/data/simple-parse-bench.json`, `quickwit/quickwit-doc-mapper/benches/data/simple-routing-expression-bench.json`, `quickwit/quickwit-indexing/benches/data/bench_data.json`, `quickwit/quickwit-indexing/benches/data/bench_data_heavy_transform.json`, `quickwit/quickwit-indexing/benches/data/bench_data_light_transform.json`, … (+3 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 5 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

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

What to do

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

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

Do you agree with this assessment?

D30 · Dependency Vulnerabilities1.4 / 10Critical✓ Tool-verified

What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.

Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `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, npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.

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

28 finding(s): 0 critical, 8 high, 19 medium, 1 low.

REDACTED

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

What to do

Resolve the 8 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (7), REDACTED. — One of this dimension's main actionable groups (8 issue-level).
Resolve the 7 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (7). — One of this dimension's main actionable groups (7 warning-level).
Resolve the 5 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED (5). — One of this dimension's main actionable groups (5 warning-level).

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

Do you agree with this assessment?

D31 · IaC & Container Security2.4 / 10Critical✓ Tool-verified

What it measures: Whether Dockerfiles / Terraform / Kubernetes config follow security best practices.

Method: IaC/container misconfiguration scan via trivy config (REDACTED/Terraform/K8s/Helm/CloudFormation); severity rules to 0-10 moderate normalizer. NotApplicable without manifests. Exhaustive, deterministic.

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

32 finding(s): 1 critical, 17 high, 12 medium, 2 low.

REDACTED

What to do

Resolve the 17 High IaC finding(s) in IaC & Container Security — start with REDACTED (7), REDACTED (5), REDACTED (2). — One of this dimension's main actionable groups (17 issue-level).
Resolve the 12 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (3), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (12 warning-level).
Resolve the 1 Critical IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).

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

Do you agree with this assessment?

D34 · Knowledge Freshness9.5 / 10Adequategated by 3 critical findings✓ Tool-verified

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.

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

24 of 505 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is quickwit/quickwit-serve/src/openapi.rs. Counted over 505 of the 621 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned knowledge · ×3quickwit/quickwit-serve/src/openapi.rs

Further orphaned files (smaller)

What to do

Resolve the 3 Orphaned knowledge finding(s) in Knowledge Freshness — start with openapi.rs, model.rs, doc_file_reader.rs. — One of this dimension's main actionable groups (3 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.

Do you agree with this assessment?

D35 · Change Coupling9.8 / 10Stronggated by 11 serious findings✓ Tool-verified

What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.

Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.

Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.

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

Strongest change-coupling: mod.rs↔mod.rs 80%; tests.rs↔lib.rs 67%; lib.rs↔mod.rs 67%

Change coupling: mod.rs ↔ mod.rs · ×11quickwit/quickwit-proto/src/control_plane/mod.rs

What to do

Resolve the 11 Change coupling finding(s) in Change Coupling — start with control_plane.rs (2), mod.rs, tests.rs. — One of this dimension's main actionable groups (11 warning-level).

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

Do you agree with this assessment?

D36 · Supply-chain Provenance & Signing2.5 / 10Weak✓ Tool-verified

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.

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

1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).

REDACTED

What to do

Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).

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

Do you agree with this assessment?

D37 · Vulnerability-disclosure Policy10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.

Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.

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

A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.

✓ On the Gold path — maintain.

Detailed fixes: d37_recommendation.md.

Do you agree with this assessment?

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

What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.

Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.

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

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

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

Do you agree with this assessment?

Frontend & cross-cutting dimensions

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

AC1 · Text alternatives10.0 / 10Exemplary○ Nothing flagged

Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.

Do you agree with this assessment?

AC2 · Forms & labels7.8 / 10Strong✓ 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 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) — quickwit/quickwit-ui/src/components/IndexSideBar.tsx:84, quickwit/quickwit-ui/src/components/QueryEditor/AggregationEditor.tsx:346, quickwit/quickwit-ui/src/components/QueryEditor/AggregationEditor.tsx:361
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) — quickwit/quickwit-ui/src/components/QueryEditor/AggregationEditor.tsx:86, quickwit/quickwit-ui/src/components/QueryEditor/AggregationEditor.tsx:300

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.

Do you agree with this assessment?

AC3 · Page structure7.7 / 10Strong✓ Tool-verified

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

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

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

The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×2) — quickwit/dependency-licenses.html:1, REDACTED:1
A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. (×2) — quickwit/dependency-licenses.html:1, REDACTED:1

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.

Do you agree with this assessment?

AC6 · Visual & motion safety10.0 / 10Exemplary○ Nothing flagged

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 — your Biome config enables no a11y rules and there's no axe/pa11y/Lighthouse in tests or CI. Start by turning on Biome's own a11y rule group to catch issues at author time. What was searched, so you can tell an absence from a miss: the 30 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 you already use: enable Biome's a11y rule group in your biome.json `linter.rules` (it is off whenever `recommended` is false and the group is unlisted), then assert with @axe-core/playwright in tests, then gate axe/pa11y/Lighthouse in CI.

Do you agree with this assessment?

AX10 · Code composition10.0 / 10Exemplary✓ Tool-verified

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

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

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

What to do

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

Do you agree with this assessment?

AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).

Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

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

Do you agree with this assessment?

DM4 · Rich vs anemic domain model10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether domain entities own their behaviour (invariant-enforcing commands) rather than being data-only structs driven by a foreign service.

Method: Roslyn (DDD-gated): entity method BODIES classified mutator-vs-query — only methods that mutate the entity's own declared state count as invariant-protecting behaviour, so a getter/passthrough doesn't rescue an anemic class. Deterministic, exhaustive over domain-layer entities.

Coverage: Population: entities by name/base convention; rich-vs-anemic judged by classifying each method body mutator-vs-query — logic-bearing domain types outside the convention are invisible.

Do you agree with this assessment?

DM5 · Encapsulated state6.8 / 10Strong✓ Tool-verified

Other · Domain Modelling — Whether a domain type's identity-bearing field stays immutable — a `pub` mutable field under a hand-rolled Hash/PartialEq breaks the value-identity invariant.

Method: Roslyn (DDD-gated): entities scanned for publicly writable state — public setters, and (C#/VB) own mutable collections handed out through an auto-property, a public field or a bare-field expression getter, where a computed/copying getter is never charged. One finding per entity; score softened when Marten/EF rehydration frameworks present. Deterministic, framework-aware.

Coverage: Population: entities by convention; encapsulation (setter shape) checked exhaustively within the set.

`IndexUid` implements a hand-rolled `Hash`/`PartialEq` (identity semantics) over a `pub` mutable id/hash field — mutating it after the value is placed in a set/map silently corrupts the collection. Make the identity field private + immutable (set once in the constructor). — quickwit/quickwit-proto/src/types/index_uid.rs:31

What to do

Make the id/hash field private and immutable — value identity must be stable for the lifetime of the value.

Do you agree with this assessment?

DM6 · Domain ↔ infrastructure boundary10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies — a domain aggregate fused to a persistence ORM (diesel/sea-orm/sqlx) on its own declaration (active-record) couples the domain to infrastructure. The clean-architecture dependency rule.

Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES — resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.

Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES — rename the layer and the check evaporates.

Do you agree with this assessment?

ES1 · Fold determinism10.0 / 10Exemplary✓ Tool-verified

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.

Do you agree with this assessment?

ES2 · Immutable events10.0 / 10Exemplary✓ Tool-verified

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.

Do you agree with this assessment?

M1 · Documentation (README)8.0 / 10Strong✓ Tool-verified

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

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

What to do

Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Add a README to the 25 of 37 project(s) that lack one — worth up to 1.4 pts.

Do you agree with this assessment?

M2 · Architecture documentation5.0 / 10Adequate✓ Tool-verified

Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.

Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.

No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.

What to do

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

Do you agree with this assessment?

M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

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

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

Do you agree with this assessment?

M4 · Documentation accuracy10.0 / 10Exemplary◐ Sampled · advisory

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.

Do you agree with this assessment?

P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

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?

P2 · Observability9.8 / 10Exemplary✓ Tool-verified

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

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

Only 28/30 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `quickwit/quickwit-metastore-utils`, `quickwit/quickwit-metrics-inventory`.

What to do

Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.

Do you agree with this assessment?

P3 · Security & performance tooling8.0 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).

Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.

What to do

Dependabot is configured but does not watch `pip` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.

Do you agree with this assessment?

P4 · Deployment & Rollback10.0 / 10Exemplary✓ Tool-verified

Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.

Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.

Do you agree with this assessment?

P5 · DR & Backup7.0 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.

Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.

What to do

Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).

Do you agree with this assessment?

P6 · Release Hygiene10.0 / 10Exemplary✓ Tool-verified

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

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

Do you agree with this assessment?

P7 · Outbound HTTP resilience3.0 / 10Weak✓ Tool-verified

Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.

Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.

`reqwest::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. — quickwit/quickwit-indexing/src/source/pulsar_source.rs:624

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.

Do you agree with this assessment?

P8 · Schema migrations10.0 / 10Exemplary○ Nothing flagged

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.

Do you agree with this assessment?

PF3 · Async & latency hygiene6.0 / 10Adequate✓ Tool-verified

Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.

Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin) 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.

`try_from_indexes_metadata` is async and calls block_on — a blocking call inside async code stalls the executor thread, and every task scheduled on it for as long as it runs. (×2) — quickwit/quickwit-metastore/src/metastore/mod.rs:299, quickwit/quickwit-metastore/src/metastore/mod.rs:354
`deserialize_indexes_metadata` is async and calls block_on — a blocking call inside async code stalls the executor thread, and every task scheduled on it for as long as it runs. (×2) — quickwit/quickwit-metastore/src/metastore/mod.rs:305, quickwit/quickwit-metastore/src/metastore/mod.rs:359

What to do

Rust: `.await` the future instead of `block_on` (on a Tokio runtime thread it panics outright) and use `tokio::time::sleep(..).await` instead of `std::thread::sleep`; where synchronous code must run, move it to `tokio::task::spawn_blocking` or `block_in_place`.

Do you agree with this assessment?

R1 · Type Safety7.8 / 10Strong✓ Tool-verified

React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.

Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.

What to do

Migrate the remaining .js/.jsx files to TypeScript.

Do you agree with this assessment?

R10 · Code Duplication9.5 / 10Exemplary✓ Tool-verified

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

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

quickwit/quickwit-ui/src/components/TimeRangeSelect.tsx:233 · quickwit/quickwit-ui/src/components/TimeRangeSelect.tsx:252 — 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. — quickwit/quickwit-ui/src/components/TimeRangeSelect.tsx:233
quickwit/quickwit-ui/src/components/QueryEditor/AggregationEditor.tsx:189 · quickwit/quickwit-ui/src/components/QueryEditor/AggregationEditor.tsx:204 — 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. — quickwit/quickwit-ui/src/components/QueryEditor/AggregationEditor.tsx:189
quickwit/quickwit-ui/src/components/SideBar.tsx:95 · quickwit/quickwit-ui/src/components/SideBar.tsx:105 — 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. — quickwit/quickwit-ui/src/components/SideBar.tsx:95
quickwit/quickwit-ui/src/views/NodeInfoView.tsx:65 · quickwit/quickwit-ui/src/views/NodeInfoView.tsx:75 — 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. — quickwit/quickwit-ui/src/views/NodeInfoView.tsx:65

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.

Do you agree with this assessment?

R2 · Cyclomatic Complexity10.0 / 10Exemplary✓ Tool-verified

React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.

Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.

parseSearchUrl has cyclomatic complexity 11 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — quickwit/quickwit-ui/src/utils/urls.ts:28

Do you agree with this assessment?

R3 · Large Files10.0 / 10Exemplary✓ Tool-verified

React / JS · Code Health — How many source files exceed the large-file threshold.

Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.

Do you agree with this assessment?

R4 · Test Coverage9.1 / 10Exemplary✓ Tool-verified

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

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

No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×3) — quickwit/quickwit-ui/src/providers/EditorProvider.tsx, quickwit/quickwit-ui/src/index.tsx, quickwit/quickwit-ui/jest/setup.js

What to do

Add tests that import the unreached modules (directly or through their public entry).

Do you agree with this assessment?

R6 · Tooling10.0 / 10Exemplary✓ Tool-verified

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

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

Do you agree with this assessment?

R7 · Dead Code9.2 / 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 7 application, 3 tooling and 11 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 (7 application, 3 tooling, 11 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 — quickwit/quickwit-ui/src/providers/EditorProvider.tsx
Nothing imports this binding — it is safe to review for removal. (×7) — quickwit/quickwit-ui/src/components/QueryEditor/config.ts:183, quickwit/quickwit-ui/src/utils/models.ts:43, quickwit/quickwit-ui/src/utils/models.ts:242, …

What to do

Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.

Do you agree with this assessment?

R8 · Dependency Hygiene6.5 / 10Strong✓ Tool-verified

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

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

Declared in quickwit/quickwit-ui/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)
Only test files import it — move it to devDependencies. — quickwit/quickwit-ui/src/index.test.js:16

What to do

Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.

Do you agree with this assessment?

R9 · Circular Imports10.0 / 10Exemplary✓ Tool-verified

React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.

Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.

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

Dimension	WCAG 2.2 A/AA criteria	Coverage
AC1 · Text alternatives	1.1.1, 1.2.2, 1.2.5	Partial signal
AC2 · Forms & labels	1.3.1, 3.3.2, 4.1.2	Partial signal
AC3 · Page structure	1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2	Partial signal
AC6 · Visual & motion safety	1.4.3, 2.4.7	Partial — literal CSS only
AC7 · A11y enforcement	enforcement — no page criterion	Enforcement posture (process)

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

Reference — by lens

The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.

Lens	Score	Rating	Impact
Code Health	88%	Exemplary	Solid.
Architecture	93%	Exemplary	Solid.
Maturity	78%	Strong	Solid.
Readiness	67%	Adequate — gated by P7	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security	52%	Adequate — gated by D29, D30, D31, D36	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Domain Modelling	86%	Exemplary	Solid.
Event Sourcing	100%	Exemplary	Strongest area.
Accessibility	71%	Strong	Solid.
Performance	60%	Adequate	Acceptable, with room to improve.

Unscored — 1 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.

P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.

Not evidenced — 3 control(s) we could not find positive evidence for

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

C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.

Not included — 72 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.
AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX2 Stateful singletons — not 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
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 — compose up failed (exit 1 — a container did not start, exited, or never became healthy) — no service selected; 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.
D11 Test Reliability — Test reliability not scored — polyglot repository, one half has no runner
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 — too few calls resolved to assess navigability
D32 Data Compliance (PII/GDPR) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
D6 Cohesion (LCOM4) — D6 reads a CS/VB/GO/SCALA/SWIFT/DART/JAVA/PY/KT/TS/TSX/MTS/CTS/JS/JSX/MJS/CJS/PHP class graph only — this repository's production source is .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the jest suite in quickwit/quickwit-ui/ ran and not one test passed (FAIL src/views/SearchView.test.jsx), so the coverage would describe the failed run, not the code. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.
DM1 Aggregate boundaries — this Rust crate declares no domain aggregate (a struct with private state and its own command methods), so DM1's aggregate-boundary read has no population to be taken over
DM2 Strongly-typed ids — the crate defines newtype typed-ids but declares no domain aggregate that could carry an id — so DM2's adoption ratio has no population to be taken over
DM3 Integration-event coupling — not scored — a domain type leaking across a crate boundary cannot be told apart from source alone from a legitimate shared-kernel crate. Reported as guidance rather than measured
DM7 Repository granularity — not scored — detecting 'a repository per CHILD entity' needs the aggregate-root structure, which is not resolvable from source alone here. Reported as guidance rather than measured
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
P10 Library API & versioning — 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
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 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
PF2 Allocation hygiene — 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
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
R5 Dependency Freshness — uses a yarn lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
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
X10 Duplicated predicate — 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.
X29 Per-element action decided by a fixed element — 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 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.
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
X6 Hand-rolled structured-format parsing — 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 — 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
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 62 finding(s)

D31 · IaC & Container Security · High IaC · ×17

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D30 · Dependency Vulnerabilities · High CVE · ×8

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED
REDACTED

D34 · Knowledge Freshness · Orphaned knowledge · ×3

Orphaned knowledge quickwit/quickwit-serve/src/openapi.rs — No living knowledge remains for this large file — its last meaningful change has decayed away, so if it breaks, no one currently understands it. It does carry its own tests, so the behaviour is pinned even though the understanding is gone: schedule a read-through, using those tests as the specification, before the next change lands here.
Orphaned knowledge quickwit/quickwit-serve/src/jaeger_api/model.rs — No living knowledge remains for this large file — its last meaningful change has decayed away, so if it breaks, no one currently understands it. It does carry its own tests, so the behaviour is pinned even though the understanding is gone: schedule a read-through, using those tests as the specification, before the next change lands here.
Orphaned knowledge quickwit/quickwit-indexing/src/source/doc_file_reader.rs — No living knowledge remains for this large file — its last meaningful change has decayed away, so if it breaks, no one currently understands it. It does carry its own tests, so the behaviour is pinned even though the understanding is gone: schedule a read-through, using those tests as the specification, before the next change lands here.

AC3 · Page structure · <html> without a lang · ×2

<html> without a lang quickwit/dependency-licenses.html:1 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang REDACTED:1 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").

AC3 · Page structure · Document without a <title> · ×2

Document without a <title> quickwit/dependency-licenses.html:1 — A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
Document without a <title> REDACTED:1 — A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED

D29 · Static Analysis (SAST) · REDACTED · ×2

REDACTED
REDACTED

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D31 · IaC & Container Security · Critical IaC · ×1

REDACTED

DM5 · Encapsulated state · Mutable field under value identity · ×1

Mutable field under value identity: IndexUid quickwit/quickwit-proto/src/types/index_uid.rs:31 — `IndexUid` implements a hand-rolled `Hash`/`PartialEq` (identity semantics) over a `pub` mutable id/hash field — mutating it after the value is placed in a set/map silently corrupts the collection. Make the identity field private + immutable (set once in the constructor).

Serious — 539 finding(s)

D17 · Explicit Debt · TodoComment · ×206

TodoComment quickwit/quickwit-actors/src/spawn_builder.rs:405 — // TODO the no advance time guard for finalize has a race condition. Ideally we would — 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 quickwit/quickwit-actors/src/actor_handle.rs:422 — // TODO investigate why Universe::with_accelerated_time() does not work 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 quickwit/quickwit-actors/src/actor_context.rs:38 — // TODO hide all of this public stuff — 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 quickwit/quickwit-cli/src/tool.rs:784 — // TODO fixme. The way we wait today is a bit lame: if the indexing pipeline exits, we will — 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 quickwit/quickwit-cli/src/split.rs:299 — // TODO: plug tags. — 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 quickwit/quickwit-cli/src/split.rs:359 — // TODO: if we have access to the storage, we could fetch that. — 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 quickwit/quickwit-cli/src/service.rs:127 — // TODO move in serve quickwit? — 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 quickwit/quickwit-cli/src/index.rs:515 — // TODO: nice to have: check first if the index exists by send a GET request, if we get a 404, — 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 quickwit/quickwit-cli/src/index.rs:1061 — // TODO(#5604) remove unwrap
TodoComment quickwit/quickwit-cli/tests/helpers.rs:212 — // TODO: refactor when we have a singleton storage resolver. — 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 quickwit/quickwit-cli/tests/helpers.rs:289 — /// TODO: this should be part of the test env setup — 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 quickwit/quickwit-cli/tests/cli.rs:911 — // TODO: edit split update timestamps and remove this sleep. — 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 quickwit/quickwit-cluster/src/member.rs:80 — // TODO: Expose more accurate size of the state in Chitchat. — 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 quickwit/quickwit-cluster/src/cluster.rs:1104 — // TODO: increase it back to 1000 when https://github.com/quickwit-oss/chitchat/issues/81 is fixed
TodoComment quickwit/quickwit-codegen/src/codegen.rs:858 — // TODO: remove this field once `check_connectivity` is used for all services. — 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 quickwit/quickwit-codegen/src/codegen.rs:1273 — // TODO: remove this field once `check_connectivity` is used for all services. — 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 quickwit/quickwit-common/src/rate_limited_tracing.rs:15 — // TODO coasetime has a recent() instead of now() which is essentially free (atomic read instead of — 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 quickwit/quickwit-common/src/rate_limited_tracing.rs:230 — // TODO as this is atomic code, we should test it with multiple threads to verify it behaves — 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 quickwit/quickwit-common/src/binary_heap.rs:19 — // TODO: Remove this once `BinaryHeap::into_iter_sorted` is stabilized. — 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 quickwit/quickwit-common/src/alloc_tracker.rs:55 — // TODO: We use a load factor of 0.5 to avoid resizing. There is no — 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 quickwit/quickwit-common/src/tower/transport.rs:268 — // TODO: Move the test 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 quickwit/quickwit-common/src/tower/metrics.rs:222 — // TODO: Remove `service` in a future breaking release. — 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 quickwit/quickwit-opentelemetry/src/otlp/metrics.rs:23 — // TODO: Remove `service` in a future breaking release. — 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 quickwit/quickwit-common/src/tower/change.rs:16 — // TODO: Remove when the next version of tower (0.4.14?) is released. — 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 quickwit/quickwit-config/src/metastore_config.rs:134 — // TODO: Implement this method when we end up storing secrets in the — 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.
+ 181 more in this group — see findings.md.

D3 · God Classes · FileTooLong · ×29

FileTooLong: postgres/metastore.rs quickwit/quickwit-metastore/src/metastore/postgres/metastore.rs — FileTooLong — 1535 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 80% of them inside a single declaration: PostgresqlMetastore (5 blocks, 91-2005). The bar is 500 significant lines; this is 1035 over it, 3.07× 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/leaf.rs quickwit/quickwit-search/src/leaf.rs — FileTooLong — 1509 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 38 free functions. The bar is 500 significant lines; this is 1009 over it, 3.02× 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/root.rs quickwit/quickwit-search/src/root.rs — FileTooLong — 1286 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 38 free functions. The bar is 500 significant lines; this is 786 over it, 2.57× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/lib.rs quickwit/quickwit-serve/src/lib.rs — FileTooLong — 1199 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 699 over it, 2.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/codegen.rs quickwit/quickwit-codegen/src/codegen.rs — FileTooLong — 986 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 486 over it, 1.97× 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: ingest/ingest_controller.rs quickwit/quickwit-control-plane/src/ingest/ingest_controller.rs — FileTooLong — 930 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 69% of them inside a single declaration: IngestController (3 blocks, 299-1358). The bar is 500 significant lines; this is 430 over it, 1.86× 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: object_storage/s3_compatible_storage.rs quickwit/quickwit-storage/src/object_storage/s3_compatible_storage.rs — FileTooLong — 903 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 71% of them inside a single declaration: S3CompatibleObjectStorage (5 blocks, 97-1163). The bar is 500 significant lines; this is 403 over it, 1.81× 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: elasticsearch_api/rest_handler.rs quickwit/quickwit-serve/src/elasticsearch_api/rest_handler.rs — FileTooLong — 898 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 50 free functions. The bar is 500 significant lines; this is 398 over it, 1.80× 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/index.rs quickwit/quickwit-cli/src/index.rs — FileTooLong — 891 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 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: file_backed/mod.rs quickwit/quickwit-metastore/src/metastore/file_backed/mod.rs — FileTooLong — 891 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 89% of them inside a single declaration: FileBackedMetastore (5 blocks, 147-1335). The bar is 500 significant lines; this is 391 over it, 1.78× 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: doc_mapper/mapping_tree.rs quickwit/quickwit-doc-mapper/src/doc_mapper/mapping_tree.rs — FileTooLong — 890 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 390 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: src/collector.rs quickwit/quickwit-search/src/collector.rs — FileTooLong — 857 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 357 over it, 1.71× 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: ingest_v2/ingester.rs quickwit/quickwit-ingest/src/ingest_v2/ingester.rs — FileTooLong — 803 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 82% of them inside a single declaration: Ingester (4 blocks, 94-1035). The bar is 500 significant lines; this is 303 over it, 1.61× 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 quickwit/quickwit-jaeger/src/lib.rs — FileTooLong — 800 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 300 over it, 1.60× 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: actors/indexing_service.rs quickwit/quickwit-indexing/src/actors/indexing_service.rs — FileTooLong — 785 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 90% of them inside a single declaration: IndexingService (11 blocks, 105-1054). The bar is 500 significant lines; this is 285 over it, 1.57× 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/tool.rs quickwit/quickwit-cli/src/tool.rs — FileTooLong — 769 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 269 over it, 1.54× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/control_plane.rs quickwit/quickwit-control-plane/src/control_plane.rs — FileTooLong — 689 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: ControlPlane (21 blocks, 89-1052). The bar is 500 significant lines; this is 189 over it, 1.38× 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: otlp/traces.rs quickwit/quickwit-opentelemetry/src/otlp/traces.rs — FileTooLong — 674 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 174 over it, 1.35× 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: indexing_scheduler/mod.rs quickwit/quickwit-control-plane/src/indexing_scheduler/mod.rs — FileTooLong — 641 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 141 over it, 1.28× 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: metastore/mod.rs quickwit/quickwit-metastore/src/metastore/mod.rs — FileTooLong — 635 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 135 over it, 1.27× 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: node_config/mod.rs quickwit/quickwit-config/src/node_config/mod.rs — FileTooLong — 625 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 125 over it, 1.25× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: scheduling/mod.rs quickwit/quickwit-control-plane/src/indexing_scheduler/scheduling/mod.rs — FileTooLong — 615 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 115 over it, 1.23× 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: doc_mapper/field_mapping_entry.rs quickwit/quickwit-doc-mapper/src/doc_mapper/field_mapping_entry.rs — FileTooLong — 595 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 95 over it, 1.19× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/top_k_collector.rs quickwit/quickwit-search/src/top_k_collector.rs — FileTooLong — 585 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 85 over it, 1.17× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/rest_client.rs quickwit/quickwit-rest-client/src/rest_client.rs — FileTooLong — 581 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 81 over it, 1.16× 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.
+ 4 more in this group — see findings.md.

D3 · God Classes · FunctionTooLong · ×14

FunctionTooLong: quickwit_serve::serve_quickwit quickwit/quickwit-serve/src/lib.rs:569 — FunctionTooLong — quickwit_serve::serve_quickwit runs 363 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 263 over it, 3.63× 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: AggregationEditor.AggregationKind quickwit/quickwit-ui/src/components/QueryEditor/AggregationEditor.tsx:113 — FunctionTooLong — AggregationKind runs 199 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 99 over it, 1.99× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: quickwit_serve::grpc::start_grpc_server quickwit/quickwit-serve/src/grpc.rs:46 — FunctionTooLong — quickwit_serve::grpc::start_grpc_server runs 179 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 79 over it, 1.79× 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: quickwit_serve::elasticsearch_api::bulk_v2::make_elastic_bulk_response_v2 quickwit/quickwit-serve/src/elasticsearch_api/bulk_v2.rs:170 — FunctionTooLong — quickwit_serve::elasticsearch_api::bulk_v2::make_elastic_bulk_response_v2 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.
FunctionTooLong: quickwit_cli::index::build_index_command quickwit/quickwit-cli/src/index.rs:50 — FunctionTooLong — quickwit_cli::index::build_index_command runs 131 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 31 over it, 1.31× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: quickwit_codegen::codegen::generate_client quickwit/quickwit-codegen/src/codegen.rs:598 — FunctionTooLong — quickwit_codegen::codegen::generate_client 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.
FunctionTooLong: SearchView.SearchView quickwit/quickwit-ui/src/views/SearchView.tsx:63 — FunctionTooLong — SearchView runs 111 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 11 over it, 1.11× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: quickwit_cli::tool::local_ingest_docs_cli quickwit/quickwit-cli/src/tool.rs:402 — FunctionTooLong — quickwit_cli::tool::local_ingest_docs_cli 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.
FunctionTooLong: quickwit_jaeger::build_search_query quickwit/quickwit-jaeger/src/lib.rs:560 — FunctionTooLong — quickwit_jaeger::build_search_query 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: quickwit_doc_mapper::doc_mapper::mapping_tree::build_mapping_from_field_type quickwit/quickwit-doc-mapper/src/doc_mapper/mapping_tree.rs:1206 — FunctionTooLong — quickwit_doc_mapper::doc_mapper::mapping_tree::build_mapping_from_field_type runs 102 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 2 over it, 1.02× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: quickwit_ingest::ingest_v2::fetch::fetch_stream_once quickwit/quickwit-ingest/src/ingest_v2/fetch.rs:411 — FunctionTooLong — quickwit_ingest::ingest_v2::fetch::fetch_stream_once runs 102 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 2 over it, 1.02× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: TimeRangeSelect.TimeRangeSelect quickwit/quickwit-ui/src/components/TimeRangeSelect.tsx:64 — FunctionTooLong — TimeRangeSelect runs 102 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 2 over it, 1.02× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: quickwit_cli::source::build_source_command quickwit/quickwit-cli/src/source.rs:33 — FunctionTooLong — quickwit_cli::source::build_source_command runs 101 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 1 over it, 1.01× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: IndexView.IndexView quickwit/quickwit-ui/src/views/IndexView.tsx:52 — FunctionTooLong — IndexView runs 101 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1 over it, 1.01× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.

D31 · IaC & Container Security · Medium IaC · ×12

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D35 · Change Coupling · Change coupling · ×11

Change coupling: mod.rs ↔ mod.rs quickwit/quickwit-proto/src/control_plane/mod.rs — `quickwit/quickwit-proto/src/control_plane/mod.rs` and `quickwit/quickwit-proto/src/ingest/mod.rs` change together 80% of the time (8 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 8 shared commits counted here, the most recent 3 are `70bfc47d` Add `code` label to gRPC metrics (#6685); `9b3873bd` Add gRPC reflection service (#5697); `d4ad40db` Removing the last extern crate macro use old idiom (#5546) — run `git show` on any of them.
Change coupling: tests.rs ↔ lib.rs quickwit/quickwit-control-plane/src/tests.rs — `quickwit/quickwit-control-plane/src/tests.rs` and `quickwit/quickwit-serve/src/lib.rs` change together 67% of the time (10 of the 15 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 10 shared commits counted here, the most recent 3 are `55840e41` fix(control-plane): Avoid spawning a new control plan loop on every s…; `f3880d52` bugfix: dont schedule indexing tasks on retiring indexers (#6427); `b4bf3c42` Exit when chitchat server fails (#5819) — run `git show` on any of them.
Change coupling: lib.rs ↔ mod.rs quickwit/quickwit-search/src/lib.rs — `quickwit/quickwit-search/src/lib.rs` and `quickwit/quickwit-serve/src/search_api/mod.rs` change together 67% of the time (8 of the 12 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 8 shared commits counted here, the most recent 3 are `4c6a293f` Remove search stream endpoint (#5886); `ddcb138f` add api endpoint to get query ast (#5212); `ba382524` Add local search CLI. (#3564) — run `git show` on any of them.
Change coupling: leaf_cache.rs ↔ root.rs quickwit/quickwit-search/src/leaf_cache.rs — `quickwit/quickwit-search/src/leaf_cache.rs` and `quickwit/quickwit-search/src/root.rs` change together 64% of the time (7 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `7062b13d` schedule leaf searches by (priority, remaining_splits) lexicographica…; `0bb78090` Forbid usage of some complex Option:: methods. (#5754); `59d5498c` document search after (#4265) — run `git show` on any of them.
Change coupling: azure_blob_storage.rs ↔ s3_compatible_storage.rs quickwit/quickwit-storage/src/object_storage/azure_blob_storage.rs — `quickwit/quickwit-storage/src/object_storage/azure_blob_storage.rs` and `quickwit/quickwit-storage/src/object_storage/s3_compatible_storage.rs` change together 58% of the time (11 of the 19 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 between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `be1054d6` Make `Storage::get_slice` zero copy for single-segment bodies (#6336); `4d0ffc32` Fix build warning (#5828); `ea35a535` Add in flight get slice metric (#5726) — run `git show` on any of them.
Change coupling: control_plane.rs ↔ shard_table.rs quickwit/quickwit-control-plane/src/control_plane.rs — `quickwit/quickwit-control-plane/src/control_plane.rs` and `quickwit/quickwit-control-plane/src/model/shard_table.rs` change together 57% of the time (13 of the 23 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 13 shared commits counted here, the most recent 3 are `0358ca36` Improve control plane logging (#6003); `f10654a2` Faster shard scaling (#5679); `69f700aa` Removing bias from shard allocation. (#5233) — run `git show` on any of them.
Change coupling: control_plane.rs ↔ shards.rs quickwit/quickwit-control-plane/src/control_plane.rs — `quickwit/quickwit-control-plane/src/control_plane.rs` and `quickwit/quickwit-metastore/src/metastore/file_backed/file_backed_index/shards.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 `f3dd8f27` Debounce shard pruning request (#5374); `948329b3` Add update timestamp to Shard model (#5332); `80351aeb` Replace handwritten getters and use macro instead — run `git show` on any of them.
Change coupling: bulk.rs ↔ rest_handler.rs quickwit/quickwit-serve/src/elasticsearch_api/bulk.rs — `quickwit/quickwit-serve/src/elasticsearch_api/bulk.rs` and `quickwit/quickwit-serve/src/elasticsearch_api/rest_handler.rs` change together 50% of the time (8 of the 16 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `8026d62c` partially implement _elastic/_cluster/health (#5595); `e5908554` box warp routes (#5540); `5df205d9` Adds recover_fn to many routes. (#5006) — run `git show` on any of them.
Change coupling: root.rs ↔ mod.rs quickwit/quickwit-search/src/root.rs — `quickwit/quickwit-search/src/root.rs` and `quickwit/quickwit-serve/src/search_api/mod.rs` change together 50% of the time (6 of the 12 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 `ddcb138f` add api endpoint to get query ast (#5212); `2d9b731d` Code simplification (#3568); `accb9315` Bypass gRPC stack when the search service is local (#3348) — run `git show` on any of them.
Change coupling: search_response_rest.rs ↔ rest.rs quickwit/quickwit-search/src/search_response_rest.rs — `quickwit/quickwit-search/src/search_response_rest.rs` and `quickwit/quickwit-serve/src/rest.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 `ddcb138f` add api endpoint to get query ast (#5212); `c9f611e2` accept post requests, plug aggregation (#1142) (at that commit the files were still `quickwit-search/src/search_response_rest.rs` and `quickwit-serve/src/rest.rs`); `1313ab50` Add errors attributes to rest search response. (#974) (at that commit the files were still `quickwit-search/src/search_response_rest.rs` and `quickwit-serve/src/rest.rs`) — run `git show` on any of them.
Change coupling: shard_positions.rs ↔ ingester.rs quickwit/quickwit-indexing/src/models/shard_positions.rs — `quickwit/quickwit-indexing/src/models/shard_positions.rs` and `quickwit/quickwit-ingest/src/ingest_v2/ingester.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 `cb5cbce9` Add more logs (#4648); `9c82b7aa` Adding more logs to diagnostic shard truncation problems. (#4635); `8e1f0bef` Initializing the shard positions actor with the existing cluster stat… — run `git show` on any of them.

D3 · God Classes · MethodTooLong · ×10

MethodTooLong: Ingester.persist_inner quickwit/quickwit-ingest/src/ingest_v2/ingester.rs:387 — MethodTooLong — persist_inner runs 231 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 131 over it, 2.31× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: PostgresqlMetastore.publish_splits quickwit/quickwit-metastore/src/metastore/postgres/metastore.rs:777 — MethodTooLong — publish_splits runs 140 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 40 over it, 1.40× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: RangeQuery.build_tantivy_ast_impl quickwit/quickwit-query/src/query_ast/range_query.rs:108 — MethodTooLong — build_tantivy_ast_impl runs 131 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 31 over it, 1.31× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: NodeConfigBuilder.build_and_validate quickwit/quickwit-config/src/node_config/serialize.rs:249 — MethodTooLong — build_and_validate runs 130 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 30 over it, 1.30× 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: IndexingPipeline.spawn_pipeline quickwit/quickwit-indexing/src/actors/indexing_pipeline.rs:315 — MethodTooLong — spawn_pipeline runs 130 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 30 over it, 1.30× 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: DocMapper.try_from quickwit/quickwit-doc-mapper/src/doc_mapper/doc_mapper_impl.rs:161 — MethodTooLong — try_from runs 104 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 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.
MethodTooLong: Uploader.handle quickwit/quickwit-indexing/src/actors/uploader.rs:269 — MethodTooLong — handle runs 104 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 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.
MethodTooLong: JaegerService.stream_spans quickwit/quickwit-jaeger/src/lib.rs:302 — MethodTooLong — stream_spans runs 102 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 2 over it, 1.02× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TantivyBoolQuery.simplify quickwit/quickwit-query/src/query_ast/tantivy_query_ast.rs:179 — MethodTooLong — simplify runs 102 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 2 over it, 1.02× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: FetchStreamTask.run quickwit/quickwit-ingest/src/ingest_v2/fetch.rs:106 — MethodTooLong — run runs 101 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 1 over it, 1.01× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.

D4 · Code Duplication · Duplicated block (8 lines × 2) · ×9

Duplicated block (8 lines × 2) quickwit/quickwit-cli/src/index.rs:434 — quickwit/quickwit-cli/src/index.rs:434-441 | quickwit/quickwit-cli/src/tool.rs:305-312 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) quickwit/quickwit-cli/src/source.rs:314 — quickwit/quickwit-cli/src/source.rs:314-321 | quickwit/quickwit-cli/src/source.rs:357-364 — 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) quickwit/quickwit-opentelemetry/src/otlp/logs.rs:325 — quickwit/quickwit-opentelemetry/src/otlp/logs.rs:325-332 | quickwit/quickwit-opentelemetry/src/otlp/traces.rs:787-794 — before extracting anything, compare `quickwit/quickwit-opentelemetry/src/otlp/logs.rs` and `quickwit/quickwit-opentelemetry/src/otlp/traces.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) quickwit/quickwit-query/src/query_ast/visitor.rs:175 — quickwit/quickwit-query/src/query_ast/visitor.rs:175-182 | quickwit/quickwit-search/src/leaf.rs:1299-1306 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) quickwit/quickwit-serve/src/otlp_api/rest_handler.rs:206 — quickwit/quickwit-serve/src/otlp_api/rest_handler.rs:206-213 | quickwit/quickwit-serve/src/otlp_api/rest_handler.rs:228-235 — 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) quickwit/quickwit-indexing/src/actors/indexing_pipeline.rs:377 — quickwit/quickwit-indexing/src/actors/indexing_pipeline.rs:377-384 | quickwit/quickwit-indexing/src/actors/merge_pipeline.rs:294-301 — before extracting anything, compare `quickwit/quickwit-indexing/src/actors/indexing_pipeline.rs` and `quickwit/quickwit-indexing/src/actors/merge_pipeline.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 57 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) quickwit/quickwit-common/src/runtimes.rs:132 — quickwit/quickwit-common/src/runtimes.rs:132-139 | quickwit/quickwit-common/src/runtimes.rs:146-153 — 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) quickwit/quickwit-cli/src/tool.rs:279 — quickwit/quickwit-cli/src/tool.rs:279-286 | quickwit/quickwit-cli/src/tool.rs:329-336 — 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) quickwit/quickwit-storage/src/object_storage/azure_blob_storage.rs:589 — quickwit/quickwit-storage/src/object_storage/azure_blob_storage.rs:589-596 | quickwit/quickwit-storage/src/opendal_storage/google_cloud_storage.rs:180-187 — 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.

D3 · God Classes · ClassTooLong · ×8

ClassTooLong: PostgresqlMetastore quickwit/quickwit-metastore/src/metastore/postgres/metastore.rs:91 — ClassTooLong — 1221 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 3 methods, 5 blocks, lines 91-2005. The bar is 400 significant lines; this is 821 over it, 3.05× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: FileBackedMetastore quickwit/quickwit-metastore/src/metastore/file_backed/mod.rs:147 — ClassTooLong — 797 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 11 methods, 5 blocks, lines 147-1335. The bar is 400 significant lines; this is 397 over it, 1.99× 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: IndexingService quickwit/quickwit-indexing/src/actors/indexing_service.rs:105 — ClassTooLong — 707 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, 11 blocks, lines 105-1054. The bar is 400 significant lines; this is 307 over it, 1.77× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Ingester quickwit/quickwit-ingest/src/ingest_v2/ingester.rs:94 — ClassTooLong — 660 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 15 methods, 4 blocks, lines 94-1035. The bar is 400 significant lines; this is 260 over it, 1.65× 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: IngestController quickwit/quickwit-control-plane/src/ingest/ingest_controller.rs:299 — ClassTooLong — 646 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 299-1358. The bar is 400 significant lines; this is 246 over it, 1.62× 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: S3CompatibleObjectStorage quickwit/quickwit-storage/src/object_storage/s3_compatible_storage.rs:97 — ClassTooLong — 642 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 20 methods, 5 blocks, lines 97-1163. The bar is 400 significant lines; this is 242 over it, 1.61× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: ControlPlane quickwit/quickwit-control-plane/src/control_plane.rs:89 — ClassTooLong — 558 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 5 methods, 21 blocks, lines 89-1052. The bar is 400 significant lines; this is 158 over it, 1.40× 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: FileBackedIndex quickwit/quickwit-metastore/src/metastore/file_backed/file_backed_index/mod.rs:54 — ClassTooLong — 425 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 32 methods, 4 blocks, lines 54-698. The bar is 400 significant lines; this is 25 over it, 1.06× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.

D4 · Code Duplication · Duplicated block (9 lines × 2) · ×8

Duplicated block (9 lines × 2) quickwit/quickwit-config/src/metastore_config.rs:59 — quickwit/quickwit-config/src/metastore_config.rs:59-67 | quickwit/quickwit-config/src/storage_config.rs:112-120 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) quickwit/quickwit-ingest/src/ingest_v2/ingester.rs:525 — quickwit/quickwit-ingest/src/ingest_v2/ingester.rs:525-533 | quickwit/quickwit-ingest/src/ingest_v2/ingester.rs:559-567 — 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) quickwit/quickwit-ingest/src/ingest_v2/mrecordlog_utils.rs:64 — quickwit/quickwit-ingest/src/ingest_v2/mrecordlog_utils.rs:64-72 | quickwit/quickwit-ingest/src/ingest_v2/mrecordlog_utils.rs:78-86 — 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) quickwit/quickwit-opentelemetry/src/otlp/logs.rs:358 — quickwit/quickwit-opentelemetry/src/otlp/logs.rs:358-366 | quickwit/quickwit-opentelemetry/src/otlp/traces.rs:621-629 — before extracting anything, compare `quickwit/quickwit-opentelemetry/src/otlp/logs.rs` and `quickwit/quickwit-opentelemetry/src/otlp/traces.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) quickwit/quickwit-proto/src/search/span_id.rs:52 — quickwit/quickwit-proto/src/search/span_id.rs:52-60 | quickwit/quickwit-proto/src/search/trace_id.rs:60-68 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) quickwit/quickwit-search/src/collector.rs:1103 — quickwit/quickwit-search/src/collector.rs:1103-1111 | quickwit/quickwit-search/src/collector.rs:1140-1150 — 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) quickwit/quickwit-opentelemetry/src/otlp/logs.rs:211 — quickwit/quickwit-opentelemetry/src/otlp/logs.rs:211-219 | quickwit/quickwit-opentelemetry/src/otlp/traces.rs:669-678 — before extracting anything, compare `quickwit/quickwit-opentelemetry/src/otlp/logs.rs` and `quickwit/quickwit-opentelemetry/src/otlp/traces.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) quickwit/quickwit-proto/src/control_plane/mod.rs:62 — quickwit/quickwit-proto/src/control_plane/mod.rs:62-73 | quickwit/quickwit-proto/src/indexing/mod.rs:63-71 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.

D17 · Explicit Debt · FixmeComment · ×7

FixmeComment quickwit/quickwit-control-plane/src/indexing_scheduler/mod.rs:308 — // FIXME — 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.
FixmeComment quickwit/quickwit-metastore/src/metastore/postgres/metastore.rs:319 — // FIXME — 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.
FixmeComment quickwit/quickwit-index-management/src/index.rs:445 — // FIXME: return an error. — 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.
FixmeComment quickwit/quickwit-metastore/src/metastore/postgres/metastore.rs:661 — // FIXME: This is not idempotent. — 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.
FixmeComment quickwit/quickwit-storage/src/cache/mod.rs:38 — /// FIXME The current approach is quite horrible in that: — 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.
FixmeComment quickwit/quickwit-storage/src/object_storage/s3_compatible_storage.rs:374 — // FIXME: This may not work on Windows. — 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.
FixmeComment quickwit/quickwit-storage/src/object_storage/s3_compatible_storage.rs:389 — // FIXME: This may not work on Windows. — 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.

D2 · Cognitive Complexity · quickwit_control_plane · ×7

quickwit_control_plane::indexing_scheduler::scheduling::convert_scheduling_solution_to_physical_plan (cognitive 32) quickwit/quickwit-control-plane/src/indexing_scheduler/scheduling/mod.rs:393 — quickwit_control_plane::indexing_scheduler::scheduling::convert_scheduling_solution_to_physical_plan has cognitive complexity 32 (threshold 15). Drivers by points: if/else 6 (20 pts), loops 6 (11 pts), boolean chains 1 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
quickwit_control_plane::indexing_scheduler::scheduling::convert_scheduling_solution_to_physical_plan_single_node_single_source (cognitive 26) quickwit/quickwit-control-plane/src/indexing_scheduler/scheduling/mod.rs:243 — quickwit_control_plane::indexing_scheduler::scheduling::convert_scheduling_solution_to_physical_plan_single_node_single_source has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (21 pts), loops 2 (4 pts), match/switch 1 (nesting depth added 14). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
quickwit_control_plane::indexing_scheduler::scheduling::convert_to_simplified_problem (cognitive 26) quickwit/quickwit-control-plane/src/indexing_scheduler/scheduling/mod.rs:918 — quickwit_control_plane::indexing_scheduler::scheduling::convert_to_simplified_problem has cognitive complexity 26 (threshold 15). Drivers by points: if/else 6 (15 pts), loops 4 (11 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
quickwit_control_plane::indexing_scheduler::format_indexing_task_map (cognitive 26) quickwit/quickwit-control-plane/src/indexing_scheduler/mod.rs:796 — quickwit_control_plane::indexing_scheduler::format_indexing_task_map has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (22 pts), loops 2 (4 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
quickwit_control_plane::indexing_scheduler::scheduling::convert_physical_plan_to_solution (cognitive 21) quickwit/quickwit-control-plane/src/indexing_scheduler/scheduling/mod.rs:135 — quickwit_control_plane::indexing_scheduler::scheduling::convert_physical_plan_to_solution has cognitive complexity 21 (threshold 15). Drivers by points: match/switch 2 (11 pts), if/else 2 (6 pts), loops 2 (4 pts) (nesting depth added 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
quickwit_control_plane::indexing_scheduler::scheduling::scheduling_logic::remove_extraneous_shards (cognitive 19) quickwit/quickwit-control-plane/src/indexing_scheduler/scheduling/scheduling_logic.rs:149 — quickwit_control_plane::indexing_scheduler::scheduling::scheduling_logic::remove_extraneous_shards has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 6 (9 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.
quickwit_control_plane::indexing_scheduler::scheduling::optimization::arrange_shards_in_home_zones (cognitive 18) quickwit/quickwit-control-plane/src/indexing_scheduler/scheduling/optimization.rs:290 — quickwit_control_plane::indexing_scheduler::scheduling::optimization::arrange_shards_in_home_zones has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (9 pts), loops 6 (9 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D30 · Dependency Vulnerabilities · Medium vulnerability · ×7

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D4 · Code Duplication · Duplicated block (7 lines × 2) · ×7

Duplicated block (7 lines × 2) quickwit/quickwit-rest-client/src/rest_client.rs:641 — quickwit/quickwit-rest-client/src/rest_client.rs:641-647 | quickwit/quickwit-rest-client/src/rest_client.rs:706-712 — 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) quickwit/quickwit-serve/src/decompression.rs:50 — quickwit/quickwit-serve/src/decompression.rs:50-56 | quickwit/quickwit-serve/src/decompression.rs:72-78 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) quickwit/quickwit-serve/src/lib.rs:1202 — quickwit/quickwit-serve/src/lib.rs:1202-1208 | quickwit/quickwit-serve/src/lib.rs:1433-1439 — 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) quickwit/quickwit-storage/src/object_storage/s3_compatible_storage.rs:254 — quickwit/quickwit-storage/src/object_storage/s3_compatible_storage.rs:254-260 | quickwit/quickwit-storage/src/opendal_storage/google_cloud_storage.rs:185-191 — 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) quickwit/quickwit-cli/src/jemalloc.rs:101 — quickwit/quickwit-cli/src/jemalloc.rs:101-107 | quickwit/quickwit-telemetry-exporters/src/logs.rs:32-38 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) quickwit/quickwit-cli/src/jemalloc.rs:180 — quickwit/quickwit-cli/src/jemalloc.rs:180-186 | quickwit/quickwit-telemetry-exporters/src/lib.rs:88-94 — 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) quickwit/quickwit-serve/src/elasticsearch_api/mod.rs:153 — quickwit/quickwit-serve/src/elasticsearch_api/mod.rs:153-159 | quickwit/quickwit-serve/src/jaeger_api/rest_handler.rs:344-350 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.

D4 · Code Duplication · Duplicated block (6 lines × 2) · ×7

Duplicated block (6 lines × 2) quickwit/quickwit-cli/src/source.rs:379 — quickwit/quickwit-cli/src/source.rs:379-384 | quickwit/quickwit-cli/src/source.rs:396-401 — 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) quickwit/quickwit-indexing/src/source/kafka_source.rs:450 — quickwit/quickwit-indexing/src/source/kafka_source.rs:450-455 | quickwit/quickwit-indexing/src/source/queue_sources/coordinator.rs:161-166 — 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) quickwit/quickwit-serve/src/lib.rs:932 — quickwit/quickwit-serve/src/lib.rs:932-937 | quickwit/quickwit-serve/src/lib.rs:952-959 — 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) quickwit/quickwit-indexing/src/actors/indexing_pipeline.rs:372 — quickwit/quickwit-indexing/src/actors/indexing_pipeline.rs:372-377 | quickwit/quickwit-indexing/src/actors/indexing_pipeline.rs:408-413 — 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) quickwit/quickwit-indexing/src/actors/indexing_pipeline.rs:345 — quickwit/quickwit-indexing/src/actors/indexing_pipeline.rs:345-350 | quickwit/quickwit-indexing/src/actors/merge_pipeline.rs:273-278 — before extracting anything, compare `quickwit/quickwit-indexing/src/actors/indexing_pipeline.rs` and `quickwit/quickwit-indexing/src/actors/merge_pipeline.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 57 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) quickwit/quickwit-cli/src/tool.rs:674 — quickwit/quickwit-cli/src/tool.rs:674-679 | quickwit/quickwit-cli/src/tool.rs:745-750 — 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) quickwit/quickwit-query/src/elastic_query_dsl/range_query.rs:109 — quickwit/quickwit-query/src/elastic_query_dsl/range_query.rs:109-114 | quickwit/quickwit-query/src/elastic_query_dsl/range_query.rs:117-122 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

D4 · Code Duplication · Duplicated block (5 lines × 2) · ×7

Duplicated block (5 lines × 2) quickwit/quickwit-metrics/src/counter.rs:204 — quickwit/quickwit-metrics/src/counter.rs:204-208 | quickwit/quickwit-metrics/src/gauge.rs:225-229 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) quickwit/quickwit-indexing/src/actors/indexing_pipeline.rs:141 — quickwit/quickwit-indexing/src/actors/indexing_pipeline.rs:141-145 | quickwit/quickwit-indexing/src/actors/merge_pipeline.rs:131-135 — before extracting anything, compare `quickwit/quickwit-indexing/src/actors/indexing_pipeline.rs` and `quickwit/quickwit-indexing/src/actors/merge_pipeline.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 57 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) quickwit/quickwit-proto/src/types/doc_uid.rs:60 — quickwit/quickwit-proto/src/types/doc_uid.rs:60-64 | quickwit/quickwit-proto/src/types/pipeline_uid.rs:71-75 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) quickwit/quickwit-opentelemetry/src/otlp/logs.rs:523 — quickwit/quickwit-opentelemetry/src/otlp/logs.rs:523-527 | quickwit/quickwit-opentelemetry/src/otlp/traces.rs:863-867 — before extracting anything, compare `quickwit/quickwit-opentelemetry/src/otlp/logs.rs` and `quickwit/quickwit-opentelemetry/src/otlp/traces.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) quickwit/quickwit-opentelemetry/src/otlp/logs.rs:529 — quickwit/quickwit-opentelemetry/src/otlp/logs.rs:529-533 | quickwit/quickwit-opentelemetry/src/otlp/traces.rs:871-875 — before extracting anything, compare `quickwit/quickwit-opentelemetry/src/otlp/logs.rs` and `quickwit/quickwit-opentelemetry/src/otlp/traces.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) quickwit/quickwit-cli/src/tool.rs:404 — quickwit/quickwit-cli/src/tool.rs:404-409 | quickwit/quickwit-cli/src/tool.rs:582-586 — 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) quickwit/quickwit-ingest/src/ingest_v2/broadcast/local_shards.rs:81 — quickwit/quickwit-ingest/src/ingest_v2/broadcast/local_shards.rs:81-85 | quickwit/quickwit-ingest/src/ingest_v2/broadcast/local_shards.rs:88-92 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

D15 · Churn × Complexity Hotspots · Hotspot · ×6

Hotspot: quickwit/quickwit-serve/src/lib.rs quickwit/quickwit-serve/src/lib.rs:569 — quickwit/quickwit-serve/src/lib.rs changed 17 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 32 in quickwit_serve::serve_quickwit at line 569. 2 of those changes were fix/bug commits, and the other 15 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 20:55:38 +00:00' --until='2026-09-28 20:55:38 +00:00' --full-history --no-merges -- quickwit/quickwit-serve/src/lib.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: quickwit/quickwit-ingest/src/ingest_v2/ingester.rs quickwit/quickwit-ingest/src/ingest_v2/ingester.rs:387 — quickwit/quickwit-ingest/src/ingest_v2/ingester.rs changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in Ingester::persist_inner at line 387. 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-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 20:55:38 +00:00' --until='2026-09-28 20:55:38 +00:00' --full-history --no-merges -- quickwit/quickwit-ingest/src/ingest_v2/ingester.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: quickwit/quickwit-metastore/src/metastore/postgres/utils.rs quickwit/quickwit-metastore/src/metastore/postgres/utils.rs:115 — quickwit/quickwit-metastore/src/metastore/postgres/utils.rs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in quickwit_metastore::metastore::postgres::utils::append_query_filters_and_order_by at line 115. 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-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 20:55:38 +00:00' --until='2026-09-28 20:55:38 +00:00' --full-history --no-merges -- quickwit/quickwit-metastore/src/metastore/postgres/utils.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: quickwit/quickwit-serve/src/grpc.rs quickwit/quickwit-serve/src/grpc.rs:46 — quickwit/quickwit-serve/src/grpc.rs changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in quickwit_serve::grpc::start_grpc_server at line 46. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 20:55:38 +00:00' --until='2026-09-28 20:55:38 +00:00' --full-history --no-merges -- quickwit/quickwit-serve/src/grpc.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: quickwit/quickwit-search/src/search_job_placer.rs quickwit/quickwit-search/src/search_job_placer.rs:193 — quickwit/quickwit-search/src/search_job_placer.rs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in SearchJobPlacer::assign_jobs_inner at line 193. 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-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 20:55:38 +00:00' --until='2026-09-28 20:55:38 +00:00' --full-history --no-merges -- quickwit/quickwit-search/src/search_job_placer.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: quickwit/quickwit-datetime/src/java_date_time_format.rs quickwit/quickwit-datetime/src/java_date_time_format.rs:221 — quickwit/quickwit-datetime/src/java_date_time_format.rs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in quickwit_datetime::java_date_time_format::match_java_date_format_token at line 221. 1 of those changes was a fix/bug commit, and the other 1 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-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 20:55:38 +00:00' --until='2026-09-28 20:55:38 +00:00' --full-history --no-merges -- quickwit/quickwit-datetime/src/java_date_time_format.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.

D4 · Code Duplication · Duplicated block (11 lines × 2) · ×6

Duplicated block (11 lines × 2) quickwit/quickwit-common/src/thread_pool/simple.rs:37 — quickwit/quickwit-common/src/thread_pool/simple.rs:37-47 | quickwit/quickwit-common/src/thread_pool/with_priority.rs:178-188 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (11 lines × 2) quickwit/quickwit-indexing/src/actors/indexing_pipeline.rs:511 — quickwit/quickwit-indexing/src/actors/indexing_pipeline.rs:511-521 | quickwit/quickwit-indexing/src/actors/merge_pipeline.rs:530-540 — before extracting anything, compare `quickwit/quickwit-indexing/src/actors/indexing_pipeline.rs` and `quickwit/quickwit-indexing/src/actors/merge_pipeline.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 57 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) quickwit/quickwit-proto/src/types/position.rs:267 — quickwit/quickwit-proto/src/types/position.rs:267-277 | quickwit/quickwit-proto/src/types/shard_id.rs:98-108 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (11 lines × 2) quickwit/quickwit-query/src/elastic_query_dsl/visitor.rs:46 — quickwit/quickwit-query/src/elastic_query_dsl/visitor.rs:46-56 | quickwit/quickwit-query/src/query_ast/visitor.rs:51-61 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (11 lines × 2) quickwit/quickwit-storage/src/object_storage/azure_blob_storage.rs:518 — quickwit/quickwit-storage/src/object_storage/azure_blob_storage.rs:518-528 | quickwit/quickwit-storage/src/object_storage/s3_compatible_storage.rs:1130-1140 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (11 lines × 2) quickwit/quickwit-macros/src/lib.rs:178 — quickwit/quickwit-macros/src/lib.rs:178-188 | quickwit/quickwit-macros/src/lib.rs:196-206 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

D5 · Coupling · Off the main sequence · ×6

Off the main sequence: quickwit-codegen — quickwit-codegen: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
Off the main sequence: quickwit-datetime — quickwit-datetime: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
Off the main sequence: quickwit-metrics — quickwit-metrics: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 20 project(s), so it's rigid to change.
Off the main sequence: quickwit-config — quickwit-config: abstractness 0.02, instability 0.14, distance 0.84 — zone of pain — concrete and depended on by 18 project(s), so it's rigid to change.
Off the main sequence: quickwit-proto — quickwit-proto: abstractness 0.07, instability 0.13, distance 0.80 — zone of pain — concrete and depended on by 20 project(s), so it's rigid to change.
Off the main sequence: quickwit-common — quickwit-common: abstractness 0.16, instability 0.04, distance 0.80 — 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.

D2 · Cognitive Complexity · quickwit_serve · ×5

quickwit_serve::serve_quickwit (cognitive 52) quickwit/quickwit-serve/src/lib.rs:569 — quickwit_serve::serve_quickwit has cognitive complexity 52 (threshold 15). Drivers by points: if/else 37 (41 pts), boolean chains 6, match/switch 1 (3 pts), loops 1 (2 pts) (nesting depth added 7). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
quickwit_serve::grpc::start_grpc_server (cognitive 35) quickwit/quickwit-serve/src/grpc.rs:46 — quickwit_serve::grpc::start_grpc_server has cognitive complexity 35 (threshold 15). Drivers by points: if/else 32 (35 pts) (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.
quickwit_serve::elasticsearch_api::rest_handler::filter_source (cognitive 26) quickwit/quickwit-serve/src/elasticsearch_api/rest_handler.rs:850 — quickwit_serve::elasticsearch_api::rest_handler::filter_source has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (19 pts), loops 3 (5 pts), match/switch 1 (2 pts) (nesting depth added 12). Most of this is not in the body itself: 4 of the 26 points are its own statements and the rest belongs to 2 function items inside it that branch (remove_path, retain_includes). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
quickwit_serve::developer_api::debug::get_node_debug_infos (cognitive 17) quickwit/quickwit-serve/src/developer_api/debug.rs:64 — quickwit_serve::developer_api::debug::get_node_debug_infos has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 4 (9 pts), if/else 5 (6 pts), loops 2 (nesting depth added 6). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
quickwit_serve::rest::get_status_with_error (cognitive 16) quickwit/quickwit-serve/src/rest.rs:603 — quickwit_serve::rest::get_status_with_error has cognitive complexity 16 (threshold 15). Drivers by points: if/else 16. 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.

D30 · Dependency Vulnerabilities · Medium advisory (unmaintained) · ×5

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D4 · Code Duplication · Duplicated block (10 lines × 2) · ×5

Duplicated block (10 lines × 2) quickwit/quickwit-codegen/src/codegen.rs:683 — quickwit/quickwit-codegen/src/codegen.rs:683-692 | quickwit/quickwit-codegen/src/codegen.rs:702-711 — 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) quickwit/quickwit-control-plane/src/control_plane.rs:695 — quickwit/quickwit-control-plane/src/control_plane.rs:695-704 | quickwit/quickwit-control-plane/src/control_plane.rs:734-743 — 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) quickwit/quickwit-metastore/src/metastore/mod.rs:325 — quickwit/quickwit-metastore/src/metastore/mod.rs:325-334 | quickwit/quickwit-metastore/src/metastore/mod.rs:375-384 — 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) quickwit/quickwit-query/src/query_ast/phrase_prefix_query.rs:56 — quickwit/quickwit-query/src/query_ast/phrase_prefix_query.rs:56-65 | quickwit/quickwit-query/src/query_ast/regex_query.rs:91-100 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) quickwit/quickwit-storage/src/object_storage/s3_compatible_storage.rs:434 — quickwit/quickwit-storage/src/object_storage/s3_compatible_storage.rs:434-443 | quickwit/quickwit-storage/src/object_storage/s3_compatible_storage.rs:591-600 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

AC2 · Forms & labels · <Select> field component without a label · ×4

<Select> field component without a label quickwit/quickwit-ui/src/components/QueryEditor/AggregationEditor.tsx:86 — 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 quickwit/quickwit-ui/src/components/QueryEditor/AggregationEditor.tsx:300 — 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 quickwit/quickwit-ui/src/components/QueryEditor/AggregationEditor.tsx:346 — 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.
<Select> field component without a label quickwit/quickwit-ui/src/components/QueryEditor/AggregationEditor.tsx:361 — 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.

D2 · Cognitive Complexity · quickwit_search · ×4

quickwit_search::leaf::run_offloaded_search_tasks (cognitive 27) quickwit/quickwit-search/src/leaf.rs:1770 — quickwit_search::leaf::run_offloaded_search_tasks has cognitive complexity 27 (threshold 15). Drivers by points: if/else 4 (13 pts), loops 4 (8 pts), match/switch 2 (6 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.
quickwit_search::leaf::normalize_timestamp_range (cognitive 25) quickwit/quickwit-search/src/leaf.rs:1129 — quickwit_search::leaf::normalize_timestamp_range has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (19 pts), boolean chains 4, match/switch 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
quickwit_search::leaf::leaf_search_single_split (cognitive 16) quickwit/quickwit-search/src/leaf.rs:682 — quickwit_search::leaf::leaf_search_single_split has cognitive complexity 16 (threshold 15). Drivers by points: if/else 14, boolean chains 1, match/switch 1. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
quickwit_search::root::convert_search_after_datetime_values (cognitive 16) quickwit/quickwit-search/src/root.rs:1498 — quickwit_search::root::convert_search_after_datetime_values has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D22 · Internal API Consistency · Duplicate intent · ×4

Duplicate intent: `kill` and `quit` appear to perform the same action (terminating the actor) with identical signatures and return types. In actor models, 'kill' usually implies forceful termination while 'quit' might be graceful, but without distinct behavioral documentation or signature differences (e.g., returning a specific error for kill vs success for quit), they are confusingly redundant. — Unify into a single method (e.g., `terminate` or `stop`) or clearly distinguish them by signature (e.g., `kill` returns an error if already dead, `quit` waits for graceful shutdown). Given the identical return type, they likely do the same thing. (signatures: ActorHandle.kill(): (ActorExitStatus, ObservableState) | ActorHandle.quit(): (ActorExitStatus, ObservableState))
Duplicate intent: `ask` and `ask_for_res` have identical signatures. The suffix `_for_res` suggests a specific return type or behavior (perhaps returning a Result directly vs wrapping it), but the signature `Result` is generic enough to cover both. This creates ambiguity for the caller. — Rename one to clarify intent (e.g., `ask` for fire-and-forget with response channel, `ask_for_res` for direct result return) or merge if they are functionally identical. (signatures: ActorContext.ask(mailbox: Mailbox, msg: M): Result | ActorContext.ask_for_res(mailbox: Mailbox, msg: M): Result)
Duplicate intent: Same as above, `Mailbox` exposes both `ask` and `ask_for_res` with identical signatures. This inconsistency propagates from `ActorContext`. — Unify into a single method or distinguish via signature. (signatures: Mailbox.ask(message: M): Result | Mailbox.ask_for_res(message: M): Result)
Duplicate intent: `search_index` and `search_index_cli` have identical signatures and likely perform the same CLI execution logic. The `_cli` suffix is redundant if both are in the CLI module. — Remove one. If `search_index` is a generic function and `search_index_cli` is a wrapper, rename the wrapper to `execute_search_cli` or similar to distinguish intent. (signatures: quickwit_cli.index.search_index(args: SearchIndexArgs): Result | quickwit_cli.index.search_index_cli(args: SearchIndexArgs): Result)

PF3 · Async & latency hygiene · Sync-over-async blocking · ×4

Sync-over-async blocking quickwit/quickwit-metastore/src/metastore/mod.rs:299 — `try_from_indexes_metadata` is async and calls block_on — a blocking call inside async code stalls the executor thread, and every task scheduled on it for as long as it runs.
Sync-over-async blocking quickwit/quickwit-metastore/src/metastore/mod.rs:305 — `deserialize_indexes_metadata` is async and calls block_on — a blocking call inside async code stalls the executor thread, and every task scheduled on it for as long as it runs.
Sync-over-async blocking quickwit/quickwit-metastore/src/metastore/mod.rs:354 — `try_from_indexes_metadata` is async and calls block_on — a blocking call inside async code stalls the executor thread, and every task scheduled on it for as long as it runs.
Sync-over-async blocking quickwit/quickwit-metastore/src/metastore/mod.rs:359 — `deserialize_indexes_metadata` is async and calls block_on — a blocking call inside async code stalls the executor thread, and every task scheduled on it for as long as it runs.

D1 · Cyclomatic Complexity · quickwit_serve · ×3

quickwit_serve::serve_quickwit (cyclomatic 32) quickwit/quickwit-serve/src/lib.rs:569 — quickwit_serve::serve_quickwit has cyclomatic complexity 32 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
quickwit_serve::grpc::start_grpc_server (cyclomatic 18) quickwit/quickwit-serve/src/grpc.rs:46 — quickwit_serve::grpc::start_grpc_server has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
quickwit_serve::rest::get_status_with_error (cyclomatic 16) quickwit/quickwit-serve/src/rest.rs:603 — quickwit_serve::rest::get_status_with_error has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D2 · Cognitive Complexity · DocMapper · ×3

DocMapper::doc_to_json (cognitive 29) quickwit/quickwit-doc-mapper/src/doc_mapper/doc_mapper_impl.rs:574 — DocMapper::doc_to_json has cognitive complexity 29 (threshold 15). Drivers by points: if/else 10 (24 pts), loops 2 (5 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.
DocMapper::try_from (cognitive 24) quickwit/quickwit-doc-mapper/src/doc_mapper/doc_mapper_impl.rs:161 — DocMapper::try_from has cognitive complexity 24 (threshold 15). Drivers by points: if/else 14 (19 pts), loops 4, boolean chains 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.
DocMapper::doc_from_json_obj (cognitive 16) quickwit/quickwit-doc-mapper/src/doc_mapper/doc_mapper_impl.rs:496 — DocMapper::doc_from_json_obj has cognitive complexity 16 (threshold 15). Drivers by points: loops 3 (9 pts), if/else 5 (6 pts), boolean chains 1 (nesting depth added 7). 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.

D2 · Cognitive Complexity · quickwit_doc_mapper · ×3

quickwit_doc_mapper::doc_mapper::mapping_tree::extract_json_val (cognitive 24) quickwit/quickwit-doc-mapper/src/doc_mapper/mapping_tree.rs:449 — quickwit_doc_mapper::doc_mapper::mapping_tree::extract_json_val has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (17 pts), loops 2 (6 pts), match/switch 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
quickwit_doc_mapper::doc_mapper::mapping_tree::build_mapping_tree_from_entries (cognitive 23) quickwit/quickwit-doc-mapper/src/doc_mapper/mapping_tree.rs:1017 — quickwit_doc_mapper::doc_mapper::mapping_tree::build_mapping_tree_from_entries has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 4 (7 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
quickwit_doc_mapper::doc_mapper::mapping_tree::extract_val_from_tantivy_val (cognitive 18) quickwit/quickwit-doc-mapper/src/doc_mapper/mapping_tree.rs:511 — quickwit_doc_mapper::doc_mapper::mapping_tree::extract_val_from_tantivy_val has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (10 pts), loops 3 (4 pts), match/switch 1 (4 pts) (nesting depth added 7). Of this number, 12 points are the body's own statements and 6 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D29 · Static Analysis (SAST) · REDACTED · ×3

REDACTED
REDACTED
REDACTED

D3 · God Classes · TooManyMethods · ×3

TooManyMethods: ControlPlaneModel quickwit/quickwit-control-plane/src/model/mod.rs:54 — 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.
TooManyMethods: ListSplitsQuery quickwit/quickwit-metastore/src/metastore/mod.rs:636 — 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.
TooManyMethods: FileBackedIndex quickwit/quickwit-metastore/src/metastore/file_backed/file_backed_index/mod.rs:54 — TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.

D30 · Dependency Vulnerabilities · Medium CVE · ×3

REDACTED
REDACTED
REDACTED

D30 · Dependency Vulnerabilities · Medium advisory (unsound) · ×3

REDACTED
REDACTED
REDACTED

D4 · Code Duplication · Duplicated block (19 lines × 2) · ×3

Duplicated block (19 lines × 2) quickwit/quickwit-indexing/src/actors/indexing_pipeline.rs:202 — quickwit/quickwit-indexing/src/actors/indexing_pipeline.rs:202-220 | quickwit/quickwit-indexing/src/actors/merge_pipeline.rs:190-208 — before extracting anything, compare `quickwit/quickwit-indexing/src/actors/indexing_pipeline.rs` and `quickwit/quickwit-indexing/src/actors/merge_pipeline.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 57 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (19 lines × 2) quickwit/quickwit-janitor/src/actors/garbage_collector.rs:105 — quickwit/quickwit-janitor/src/actors/garbage_collector.rs:105-123 | quickwit/quickwit-janitor/src/actors/retention_policy_executor.rs:81-99 — 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 (19 lines × 2) quickwit/quickwit-search/src/list_fields/mod.rs:153 — quickwit/quickwit-search/src/list_fields/mod.rs:153-171 | quickwit/quickwit-search/src/list_fields/mod.rs:173-191 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

R4 · Test Coverage · No test reaches this file · ×3

No test reaches this file quickwit/quickwit-ui/src/providers/EditorProvider.tsx — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file quickwit/quickwit-ui/src/index.tsx — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file quickwit/quickwit-ui/jest/setup.js — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.

D1 · Cyclomatic Complexity · quickwit_metastore · ×2

quickwit_metastore::metastore::file_backed::file_backed_index::split_query_predicate (cyclomatic 23) quickwit/quickwit-metastore/src/metastore/file_backed/file_backed_index/mod.rs:724 — quickwit_metastore::metastore::file_backed::file_backed_index::split_query_predicate has cyclomatic complexity 23 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
quickwit_metastore::metastore::postgres::utils::append_query_filters_and_order_by (cyclomatic 20) quickwit/quickwit-metastore/src/metastore/postgres/utils.rs:115 — quickwit_metastore::metastore::postgres::utils::append_query_filters_and_order_by 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.

D2 · Cognitive Complexity · quickwit_metastore · ×2

quickwit_metastore::metastore::file_backed::file_backed_index::split_query_predicate (cognitive 25) quickwit/quickwit-metastore/src/metastore/file_backed/file_backed_index/mod.rs:724 — quickwit_metastore::metastore::file_backed::file_backed_index::split_query_predicate has cognitive complexity 25 (threshold 15). Drivers by points: if/else 14 (18 pts), boolean chains 6, match/switch 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
quickwit_metastore::metastore::postgres::metastore::build_index_id_patterns_sql_query (cognitive 17) quickwit/quickwit-metastore/src/metastore/postgres/metastore.rs:1948 — quickwit_metastore::metastore::postgres::metastore::build_index_id_patterns_sql_query has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (13 pts), loops 3, boolean chains 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · quickwit_indexing · ×2

quickwit_indexing::docs_clustering::tokenizer::is_ipv4 (cognitive 22) quickwit/quickwit-indexing/src/docs_clustering/tokenizer.rs:228 — quickwit_indexing::docs_clustering::tokenizer::is_ipv4 has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (13 pts), boolean chains 6, loops 2 (3 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.
quickwit_indexing::source::kafka_source::spawn_consumer_poll_loop (cognitive 18) quickwit/quickwit-indexing/src/source/kafka_source.rs:553 — quickwit_indexing::source::kafka_source::spawn_consumer_poll_loop has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 2 (4 pts), match/switch 1 (3 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D29 · Static Analysis (SAST) · REDACTED · ×2

REDACTED
REDACTED

D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×2

Members sharing a duplicated core (4 members, 50+ identical tokens) quickwit/quickwit-proto/src/types/doc_mapping_uid.rs:87 — quickwit/quickwit-proto/src/types/doc_mapping_uid.rs:87-113 | quickwit/quickwit-proto/src/types/doc_uid.rs:86-112 | quickwit/quickwit-proto/src/types/index_uid.rs:118-151 | quickwit/quickwit-proto/src/types/pipeline_uid.rs:90-116 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) quickwit/quickwit-serve/src/elasticsearch_api/model/error.rs:59 — quickwit/quickwit-serve/src/elasticsearch_api/model/error.rs:59-75 | quickwit/quickwit-serve/src/elasticsearch_api/model/error.rs:79-95 | quickwit/quickwit-serve/src/elasticsearch_api/model/error.rs:99-115 | quickwit/quickwit-serve/src/elasticsearch_api/model/error.rs:119-135 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.

D4 · Code Duplication · Duplicated block (17 lines × 2) · ×2

Duplicated block (17 lines × 2) quickwit/quickwit-index-management/src/index.rs:491 — quickwit/quickwit-index-management/src/index.rs:491-507 | quickwit/quickwit-index-management/src/index.rs:525-541 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) quickwit/quickwit-metastore/src/metastore/mod.rs:761 — quickwit/quickwit-metastore/src/metastore/mod.rs:761-777 | quickwit/quickwit-metastore/src/metastore/mod.rs:809-825 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

D4 · Code Duplication · Duplicated block (16 lines × 2) · ×2

Duplicated block (16 lines × 2) quickwit/quickwit-doc-mapper/src/doc_mapper/mapping_tree.rs:392 — quickwit/quickwit-doc-mapper/src/doc_mapper/mapping_tree.rs:392-407 | quickwit/quickwit-doc-mapper/src/doc_mapper/mapping_tree.rs:412-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 (16 lines × 2) quickwit/quickwit-storage/src/cache/base_cache.rs:327 — quickwit/quickwit-storage/src/cache/base_cache.rs:327-342 | quickwit/quickwit-storage/src/cache/base_cache.rs:439-454 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

D4 · Code Duplication · Duplicated block (13–14 lines × 2) · ×2

Duplicated block (13–14 lines × 2) quickwit/quickwit-indexing/src/source/kinesis/helpers.rs:21 — quickwit/quickwit-indexing/src/source/kinesis/helpers.rs:21-33 | quickwit/quickwit-indexing/src/source/queue_sources/sqs_queue.rs:204-217 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (13–14 lines × 2) quickwit/quickwit-search/src/root.rs:1259 — quickwit/quickwit-search/src/root.rs:1259-1272 | quickwit/quickwit-search/src/root.rs:1383-1395 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

D4 · Code Duplication · Duplicated block (14 lines × 2) · ×2

Duplicated block (14 lines × 2) quickwit/quickwit-opentelemetry/src/otlp/logs.rs:270 — quickwit/quickwit-opentelemetry/src/otlp/logs.rs:270-283 | quickwit/quickwit-opentelemetry/src/otlp/traces.rs:732-745 — before extracting anything, compare `quickwit/quickwit-opentelemetry/src/otlp/logs.rs` and `quickwit/quickwit-opentelemetry/src/otlp/traces.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) quickwit/quickwit-rest-client/src/rest_client.rs:444 — quickwit/quickwit-rest-client/src/rest_client.rs:444-457 | quickwit/quickwit-rest-client/src/rest_client.rs:624-637 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

D4 · Code Duplication · Duplicated block (11 lines × 3) · ×2

Duplicated block (11 lines × 3) quickwit/quickwit-proto/src/compaction/mod.rs:92 — quickwit/quickwit-proto/src/compaction/mod.rs:92-102 | quickwit/quickwit-proto/src/control_plane/mod.rs:122-132 | quickwit/quickwit-proto/src/indexing/mod.rs:105-115 — 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 (11 lines × 3) quickwit/quickwit-proto/src/types/doc_mapping_uid.rs:103 — quickwit/quickwit-proto/src/types/doc_mapping_uid.rs:103-113 | quickwit/quickwit-proto/src/types/doc_uid.rs:102-112 | quickwit/quickwit-proto/src/types/pipeline_uid.rs:106-116 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.

R10 · Code Duplication · Duplicated block (10 lines × 2 locations) · ×2

Duplicated block (10 lines × 2 locations) quickwit/quickwit-ui/src/components/SideBar.tsx:95 — quickwit/quickwit-ui/src/components/SideBar.tsx:95 · quickwit/quickwit-ui/src/components/SideBar.tsx:105 — 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 (10 lines × 2 locations) quickwit/quickwit-ui/src/views/NodeInfoView.tsx:65 — quickwit/quickwit-ui/src/views/NodeInfoView.tsx:65 · quickwit/quickwit-ui/src/views/NodeInfoView.tsx:75 — 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.

AC2 · Forms & labels · <Autocomplete> field component without a label · ×1

<Autocomplete> field component without a label quickwit/quickwit-ui/src/components/IndexSideBar.tsx:84 — 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.

AC7 · A11y enforcement · Accessibility enforcement below the top rung · ×1

Accessibility enforcement below the top rung — No accessibility enforcement found — your Biome config enables no a11y rules and there's no axe/pa11y/Lighthouse in tests or CI. Start by turning on Biome's own a11y rule group to catch issues at author time. What was searched, so you can tell an absence from a miss: the 30 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.

D1 · Cyclomatic Complexity · SortingFieldExtractorComponent · ×1

SortingFieldExtractorComponent::convert_to_u64_ff_val (cyclomatic 50) quickwit/quickwit-search/src/collector.rs:214 — SortingFieldExtractorComponent::convert_to_u64_ff_val has cyclomatic complexity 50 (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.

D1 · Cyclomatic Complexity · TantivyBoolQuery · ×1

TantivyBoolQuery::simplify (cyclomatic 30) quickwit/quickwit-query/src/query_ast/tantivy_query_ast.rs:179 — TantivyBoolQuery::simplify has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · quickwit_ingest · ×1

quickwit_ingest::ingest_v2::router::update_ingest_metrics (cyclomatic 22) quickwit/quickwit-ingest/src/ingest_v2/router.rs:507 — quickwit_ingest::ingest_v2::router::update_ingest_metrics has cyclomatic complexity 22 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.

D1 · Cyclomatic Complexity · quickwit_jaeger · ×1

quickwit_jaeger::build_search_query (cyclomatic 22) quickwit/quickwit-jaeger/src/lib.rs:560 — quickwit_jaeger::build_search_query has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · quickwit_query · ×1

quickwit_query::query_ast::user_input_query::convert_user_input_ast_to_query_ast (cyclomatic 22) quickwit/quickwit-query/src/query_ast/user_input_query.rs:97 — quickwit_query::query_ast::user_input_query::convert_user_input_ast_to_query_ast has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · AggregationEditor.AggregationKind (cyclomatic 22) · ×1

AggregationEditor.AggregationKind (cyclomatic 22) quickwit/quickwit-ui/src/components/QueryEditor/AggregationEditor.tsx:113 — AggregationEditor.AggregationKind has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 3 of the 22 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 249, 156, 123, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · Ingester · ×1

Ingester::persist_inner (cyclomatic 20) quickwit/quickwit-ingest/src/ingest_v2/ingester.rs:387 — Ingester::persist_inner has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · quickwit_doc_mapper · ×1

quickwit_doc_mapper::doc_mapper::field_mapping_entry::deserialize_mapping_type (cyclomatic 19) quickwit/quickwit-doc-mapper/src/doc_mapper/field_mapping_entry.rs:721 — quickwit_doc_mapper::doc_mapper::field_mapping_entry::deserialize_mapping_type has cyclomatic complexity 19 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.

D1 · Cyclomatic Complexity · RangeQuery · ×1

RangeQuery::build_tantivy_ast_impl (cyclomatic 19) quickwit/quickwit-query/src/query_ast/range_query.rs:108 — RangeQuery::build_tantivy_ast_impl 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.

D1 · Cyclomatic Complexity · SearchJobPlacer · ×1

SearchJobPlacer::assign_jobs_inner (cyclomatic 19) quickwit/quickwit-search/src/search_job_placer.rs:193 — SearchJobPlacer::assign_jobs_inner 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.

D1 · Cyclomatic Complexity · quickwit_cli · ×1

quickwit_cli::generate_markdown::markdown_for_command_helper (cyclomatic 18) quickwit/quickwit-cli/src/generate_markdown.rs:65 — quickwit_cli::generate_markdown::markdown_for_command_helper has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · quickwit_search · ×1

quickwit_search::leaf::normalize_timestamp_range (cyclomatic 18) quickwit/quickwit-search/src/leaf.rs:1129 — quickwit_search::leaf::normalize_timestamp_range has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · DocMapper · ×1

DocMapper::try_from (cyclomatic 16) quickwit/quickwit-doc-mapper/src/doc_mapper/doc_mapper_impl.rs:161 — DocMapper::try_from 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.

D1 · Cyclomatic Complexity · FetchStreamTask · ×1

FetchStreamTask::run (cyclomatic 16) quickwit/quickwit-ingest/src/ingest_v2/fetch.rs:106 — FetchStreamTask::run 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.

D1 · Cyclomatic Complexity · SearchView.SearchView (cyclomatic 16) · ×1

SearchView.SearchView (cyclomatic 16) quickwit/quickwit-ui/src/views/SearchView.tsx:63 — SearchView.SearchView has cyclomatic complexity 16 (threshold 15). 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 133, 81, 122, …). 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.

D17 · Explicit Debt · HackComment · ×1

HackComment quickwit/quickwit-storage/src/cache/quickwit_cache.rs:112 — /// HACK! We use `0..usize::MAX` to signify the "entire file". — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.

D2 · Cognitive Complexity · SortingFieldExtractorComponent · ×1

SortingFieldExtractorComponent::convert_to_u64_ff_val (cognitive 56) quickwit/quickwit-search/src/collector.rs:214 — SortingFieldExtractorComponent::convert_to_u64_ff_val has cognitive complexity 56 (threshold 15). Drivers by points: if/else 12 (32 pts), boolean chains 17, match/switch 4 (7 pts) (nesting depth added 23). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.

D2 · Cognitive Complexity · TantivyBoolQuery · ×1

TantivyBoolQuery::simplify (cognitive 50) quickwit/quickwit-query/src/query_ast/tantivy_query_ast.rs:179 — TantivyBoolQuery::simplify has cognitive complexity 50 (threshold 15). Drivers by points: if/else 17 (28 pts), loops 7 (9 pts), match/switch 3 (7 pts), boolean chains 6 (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.

D2 · Cognitive Complexity · S3CompatibleObjectStorage · ×1

S3CompatibleObjectStorage::bulk_delete_multi (cognitive 36) quickwit/quickwit-storage/src/object_storage/s3_compatible_storage.rs:781 — S3CompatibleObjectStorage::bulk_delete_multi has cognitive complexity 36 (threshold 15). Drivers by points: if/else 5 (17 pts), loops 4 (10 pts), match/switch 2 (8 pts), boolean chains 1 (nesting depth added 24). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · quickwit_cli · ×1

quickwit_cli::generate_markdown::markdown_for_command_helper (cognitive 34) quickwit/quickwit-cli/src/generate_markdown.rs:65 — quickwit_cli::generate_markdown::markdown_for_command_helper has cognitive complexity 34 (threshold 15). Drivers by points: if/else 12 (21 pts), loops 5 (11 pts), boolean chains 2 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · Ingester · ×1

Ingester::persist_inner (cognitive 33) quickwit/quickwit-ingest/src/ingest_v2/ingester.rs:387 — Ingester::persist_inner has cognitive complexity 33 (threshold 15). Drivers by points: if/else 12 (18 pts), loops 5 (8 pts), match/switch 3 (7 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · quickwit_opentelemetry · ×1

quickwit_opentelemetry::otlp::logs::parse_otlp_logs (cognitive 33) quickwit/quickwit-opentelemetry/src/otlp/logs.rs:357 — quickwit_opentelemetry::otlp::logs::parse_otlp_logs has cognitive complexity 33 (threshold 15). Drivers by points: if/else 10 (25 pts), loops 3 (6 pts), match/switch 1 (2 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.

D2 · Cognitive Complexity · quickwit_query · ×1

quickwit_query::query_ast::user_input_query::convert_user_input_ast_to_query_ast (cognitive 33) quickwit/quickwit-query/src/query_ast/user_input_query.rs:97 — quickwit_query::query_ast::user_input_query::convert_user_input_ast_to_query_ast has cognitive complexity 33 (threshold 15). Drivers by points: if/else 11 (19 pts), match/switch 4 (9 pts), loops 2 (5 pts) (nesting depth added 16). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.

D2 · Cognitive Complexity · KinesisSource · ×1

KinesisSource::emit_batches (cognitive 30) quickwit/quickwit-indexing/src/source/kinesis/kinesis_source.rs:219 — KinesisSource::emit_batches has cognitive complexity 30 (threshold 15). Drivers by points: if/else 5 (16 pts), loops 3 (9 pts), match/switch 2 (5 pts) (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · FetchStreamTask · ×1

FetchStreamTask::run (cognitive 30) quickwit/quickwit-ingest/src/ingest_v2/fetch.rs:106 — FetchStreamTask::run has cognitive complexity 30 (threshold 15). Drivers by points: if/else 12 (24 pts), boolean chains 3, 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.

D2 · Cognitive Complexity · quickwit_jaeger · ×1

quickwit_jaeger::build_search_query (cognitive 30) quickwit/quickwit-jaeger/src/lib.rs:560 — quickwit_jaeger::build_search_query has cognitive complexity 30 (threshold 15). Drivers by points: if/else 17 (23 pts), boolean chains 5, loops 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · SearchJobPlacer · ×1

SearchJobPlacer::assign_jobs_inner (cognitive 28) quickwit/quickwit-search/src/search_job_placer.rs:193 — SearchJobPlacer::assign_jobs_inner has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (15 pts), loops 4 (6 pts), match/switch 2 (5 pts), boolean chains 2 (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.

D2 · Cognitive Complexity · MappingLeaf · ×1

MappingLeaf::doc_from_json (cognitive 27) quickwit/quickwit-doc-mapper/src/doc_mapper/mapping_tree.rs:373 — MappingLeaf::doc_from_json has cognitive complexity 27 (threshold 15). Drivers by points: loops 5 (16 pts), if/else 6 (11 pts) (nesting depth added 16). 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.

D2 · Cognitive Complexity · IngestRouter · ×1

IngestRouter::process_persist_results (cognitive 24) quickwit/quickwit-ingest/src/ingest_v2/router.rs:276 — IngestRouter::process_persist_results has cognitive complexity 24 (threshold 15). Drivers by points: loops 4 (11 pts), if/else 3 (7 pts), match/switch 2 (6 pts) (nesting depth added 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.

D2 · Cognitive Complexity · quickwit_lambda_client · ×1

quickwit_lambda_client::deploy::garbage_collect_old_versions (cognitive 24) quickwit/quickwit-lambda-client/src/deploy.rs:517 — quickwit_lambda_client::deploy::garbage_collect_old_versions has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (19 pts), loops 3 (4 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.

D2 · Cognitive Complexity · QuickwitClient · ×1

QuickwitClient::ingest (cognitive 24) quickwit/quickwit-rest-client/src/rest_client.rs:316 — QuickwitClient::ingest has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (16 pts), match/switch 2 (4 pts), loops 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.

D2 · Cognitive Complexity · AggregationEditor.AggregationKind (cognitive 22) · ×1

AggregationEditor.AggregationKind (cognitive 22) quickwit/quickwit-ui/src/components/QueryEditor/AggregationEditor.tsx:113 — AggregationEditor.AggregationKind has cognitive complexity 22 (threshold 15). Drivers by points: if/else 16 (19 pts), boolean chains 1, loops 1, match/switch 1 (nesting depth added 3). Most of this is not in the body itself: 2 of the 22 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 249, 123, 237, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · IngestSource · ×1

IngestSource::truncate (cognitive 21) quickwit/quickwit-indexing/src/source/ingest/mod.rs:295 — IngestSource::truncate has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 4 (5 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · quickwit_macros · ×1

quickwit_macros::generate_proxy_struct (cognitive 21) quickwit/quickwit-macros/src/lib.rs:137 — quickwit_macros::generate_proxy_struct has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (11 pts), match/switch 2 (6 pts), loops 2 (4 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · quickwit_codegen · ×1

quickwit_codegen::codegen::generate_grpc_server_adapter_methods (cognitive 19) quickwit/quickwit-codegen/src/codegen.rs:1373 — quickwit_codegen::codegen::generate_grpc_server_adapter_methods has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (18 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · quickwit_directories · ×1

quickwit_directories::hot_directory::write_hotcache (cognitive 19) quickwit/quickwit-directories/src/hot_directory.rs:472 — quickwit_directories::hot_directory::write_hotcache has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 5 (8 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · FileByteRangeCacheState · ×1

FileByteRangeCacheState::put_slice (cognitive 19) quickwit/quickwit-storage/src/cache/byte_range_cache.rs:59 — FileByteRangeCacheState::put_slice has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 2, match/switch 2, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · JaegerService · ×1

JaegerService::stream_spans (cognitive 18) quickwit/quickwit-jaeger/src/lib.rs:302 — JaegerService::stream_spans has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (11 pts), loops 3, match/switch 2 (3 pts), boolean chains 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.

D2 · Cognitive Complexity · quickwit_storage · ×1

quickwit_storage::object_storage::s3_compatible_storage::convert_list_objects (cognitive 18) quickwit/quickwit-storage/src/object_storage/s3_compatible_storage.rs:1166 — quickwit_storage::object_storage::s3_compatible_storage::convert_list_objects has cognitive complexity 18 (threshold 15). Drivers by points: match/switch 4 (10 pts), if/else 3 (6 pts), boolean chains 1, loops 1 (nesting depth added 9). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.

D2 · Cognitive Complexity · IngestController · ×1

IngestController::compute_shards_to_rebalance (cognitive 17) quickwit/quickwit-control-plane/src/ingest/ingest_controller.rs:1221 — IngestController::compute_shards_to_rebalance has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (14 pts), loops 3 (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.

D2 · Cognitive Complexity · IndexingService · ×1

IndexingService::spawn_pipelines (cognitive 17) quickwit/quickwit-indexing/src/actors/indexing_service.rs:733 — IndexingService::spawn_pipelines has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (15 pts), boolean chains 1, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · quickwit_ingest · ×1

quickwit_ingest::ingest_v2::fetch::fetch_stream_once (cognitive 17) quickwit/quickwit-ingest/src/ingest_v2/fetch.rs:411 — quickwit_ingest::ingest_v2::fetch::fetch_stream_once has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (10 pts), match/switch 3 (6 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · PostgresqlMetastore · ×1

PostgresqlMetastore::indexes_metadata (cognitive 17) quickwit/quickwit-metastore/src/metastore/postgres/metastore.rs:557 — PostgresqlMetastore::indexes_metadata has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 3 (5 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · CodeTokenStreamState · ×1

CodeTokenStreamState::advance (cognitive 17) quickwit/quickwit-query/src/tokenizers/code_tokenizer.rs:162 — CodeTokenStreamState::advance has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (8 pts), match/switch 4 (7 pts), boolean chains 2 (nesting depth added 7). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.

D2 · Cognitive Complexity · quickwit_index_management · ×1

quickwit_index_management::garbage_collection::delete_splits_marked_for_deletion_several_indexes (cognitive 16) quickwit/quickwit-index-management/src/garbage_collection.rs:314 — quickwit_index_management::garbage_collection::delete_splits_marked_for_deletion_several_indexes has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 2 (3 pts), match/switch 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · Uploader · ×1

Uploader::handle (cognitive 16) quickwit/quickwit-indexing/src/actors/uploader.rs:269 — Uploader::handle has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (10 pts), match/switch 3 (4 pts), loops 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · MultiKeyOptions · ×1

MultiKeyOptions::parse (cognitive 16) quickwit/quickwit-macros/src/lib.rs:410 — MultiKeyOptions::parse has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (13 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · GenericQuickwitSegmentTopKCollector · ×1

GenericQuickwitSegmentTopKCollector::collect_top_k_block (cognitive 16) quickwit/quickwit-search/src/top_k_collector.rs:711 — GenericQuickwitSegmentTopKCollector::collect_top_k_block has cognitive complexity 16 (threshold 15). Drivers by points: loops 4 (10 pts), if/else 4 (6 pts) (nesting depth added 8). 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.

D22 · Internal API Consistency · Inconsistent naming and return types for observation · ×1

Inconsistent naming and return types for observation: `ActorContext.observe` returns `ObservableState`, while `ActorHandle.observe` returns `Observation`. `Universe.observe` returns `ActorObservation`. These types likely contain overlapping data (state, type, etc.), but the naming (`observe` vs `observe` vs `observe`) and return types vary by context, making it unclear which method to use for a given level of detail. — Standardize the return type (e.g., always return `Observation` or `ActorObservation`) and ensure method names reflect the action (e.g., `get_observation` vs `observe` if one is side-effecting). (signatures: ActorContext.observe(actor: A): ObservableState | ActorHandle.observe(): Observation | ActorHandle.process_pending_and_observe(): Observation | Universe.observe(timeout: Duration): ActorObservation)

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D3 · God Classes · TooManyFields · ×1

TooManyFields: SearchQueryParams quickwit/quickwit-serve/src/elasticsearch_api/model/search_query_params.rs:31 — TooManyFields — 49 stored fields beside 3 methods. The bar is 30 stored fields; this is 19 over it, 1.63× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.

D30 · Dependency Vulnerabilities · Medium advisory (notice) · ×1

REDACTED

D4 · Code Duplication · Duplicated block (33–34 lines × 2) · ×1

Duplicated block (33–34 lines × 2) quickwit/quickwit-jaeger/src/lib.rs:316 — quickwit/quickwit-jaeger/src/lib.rs:316-349 | quickwit/quickwit-jaeger/src/v2.rs:360-392 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.

D4 · Code Duplication · Duplicated block (34 lines × 2) · ×1

Duplicated block (34 lines × 2) quickwit/quickwit-storage/src/object_storage/azure_blob_storage.rs:423 — quickwit/quickwit-storage/src/object_storage/azure_blob_storage.rs:423-456 | quickwit/quickwit-storage/src/object_storage/s3_compatible_storage.rs:744-777 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.

D4 · Code Duplication · Duplicated block (20–21 lines × 2) · ×1

Duplicated block (20–21 lines × 2) quickwit/quickwit-indexing/src/source/kafka_source.rs:478 — quickwit/quickwit-indexing/src/source/kafka_source.rs:478-497 | quickwit/quickwit-indexing/src/source/pulsar_source.rs:236-256 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.

D4 · Code Duplication · Duplicated block (18–19 lines × 2) · ×1

Duplicated block (18–19 lines × 2) quickwit/quickwit-cli/src/index.rs:414 — quickwit/quickwit-cli/src/index.rs:414-432 | quickwit/quickwit-cli/src/tool.rs:286-303 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.

D4 · Code Duplication · Duplicated block (16 lines × 4) · ×1

Duplicated block (16 lines × 4) quickwit/quickwit-serve/src/elasticsearch_api/model/error.rs:60 — quickwit/quickwit-serve/src/elasticsearch_api/model/error.rs:60-75 | quickwit/quickwit-serve/src/elasticsearch_api/model/error.rs:80-95 | quickwit/quickwit-serve/src/elasticsearch_api/model/error.rs:100-115 | quickwit/quickwit-serve/src/elasticsearch_api/model/error.rs:120-135 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (11–14 lines × 2) · ×1

Duplicated block (11–14 lines × 2) quickwit/quickwit-search/src/list_fields/root.rs:119 — quickwit/quickwit-search/src/list_fields/root.rs:119-132 | quickwit/quickwit-search/src/list_terms.rs:119-129 — before extracting anything, compare `quickwit/quickwit-search/src/list_fields/root.rs` and `quickwit/quickwit-search/src/list_terms.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.

D4 · Code Duplication · Duplicated block (13 lines × 2) · ×1

Duplicated block (13 lines × 2) quickwit/quickwit-query/src/query_ast/wildcard_query.rs:129 — quickwit/quickwit-query/src/query_ast/wildcard_query.rs:129-141 | quickwit/quickwit-query/src/query_ast/wildcard_query.rs:148-160 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

D4 · Code Duplication · Duplicated block (12 lines × 2) · ×1

Duplicated block (12 lines × 2) quickwit/quickwit-metastore/src/split_metadata_version.rs:121 — quickwit/quickwit-metastore/src/split_metadata_version.rs:121-132 | quickwit/quickwit-metastore/src/split_metadata_version.rs:143-154 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

D4 · Code Duplication · Duplicated block (10–11 lines × 2) · ×1

Duplicated block (10–11 lines × 2) quickwit/quickwit-ingest/src/ingest_v2/routing_table.rs:260 — quickwit/quickwit-ingest/src/ingest_v2/routing_table.rs:260-270 | quickwit/quickwit-ingest/src/ingest_v2/routing_table.rs:304-313 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

D4 · Code Duplication · Duplicated block (9–10 lines × 3) · ×1

Duplicated block (9–10 lines × 3) quickwit/quickwit-query/src/query_ast/tantivy_query_ast.rs:203 — quickwit/quickwit-query/src/query_ast/tantivy_query_ast.rs:203-211 | quickwit/quickwit-query/src/query_ast/tantivy_query_ast.rs:222-230 | quickwit/quickwit-query/src/query_ast/tantivy_query_ast.rs:244-253 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (7–10 lines × 3) · ×1

Duplicated block (7–10 lines × 3) quickwit/quickwit-search/src/list_fields/root.rs:123 — quickwit/quickwit-search/src/list_fields/root.rs:123-132 | quickwit/quickwit-search/src/list_terms.rs:121-129 | quickwit/quickwit-search/src/root.rs:810-816 — before extracting anything, compare `quickwit/quickwit-search/src/list_fields/root.rs` and `quickwit/quickwit-search/src/list_terms.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.

D4 · Code Duplication · Duplicated block (9–10 lines × 2) · ×1

Duplicated block (9–10 lines × 2) quickwit/quickwit-search/src/list_fields/root.rs:157 — quickwit/quickwit-search/src/list_fields/root.rs:157-166 | quickwit/quickwit-search/src/list_terms.rs:187-195 — before extracting anything, compare `quickwit/quickwit-search/src/list_fields/root.rs` and `quickwit/quickwit-search/src/list_terms.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.

D4 · Code Duplication · Duplicated block (33 lines × 2) · ×1

Duplicated block (33 lines × 2) quickwit/quickwit-codegen/example/src/error.rs:40 — quickwit/quickwit-codegen/example/src/error.rs:40-86 | quickwit/quickwit-proto/src/developer/mod.rs:42-74 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.

D4 · Code Duplication · Duplicated block (8 lines × 3) · ×1

Duplicated block (8 lines × 3) quickwit/quickwit-compaction/src/compaction_pipeline.rs:85 — quickwit/quickwit-compaction/src/compaction_pipeline.rs:85-92 | quickwit/quickwit-indexing/src/actors/indexing_pipeline.rs:100-107 | quickwit/quickwit-indexing/src/actors/merge_pipeline.rs:86-93 — before extracting anything, compare `quickwit/quickwit-indexing/src/actors/indexing_pipeline.rs` and `quickwit/quickwit-indexing/src/actors/merge_pipeline.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 57 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (8 lines × 6) · ×1

Duplicated block (8 lines × 6) quickwit/quickwit-config/src/metastore_config.rs:74 — quickwit/quickwit-config/src/metastore_config.rs:74-81 | quickwit/quickwit-config/src/storage_config.rs:127-134 | quickwit/quickwit-config/src/storage_config.rs:136-143 | quickwit/quickwit-config/src/storage_config.rs:145-152 | quickwit/quickwit-config/src/storage_config.rs:154-161 | quickwit/quickwit-config/src/storage_config.rs:163-170 — there are 6 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 6 sites; resolving a subset leaves the remainder to drift apart.

D4 · Code Duplication · Duplicated block (15 lines × 2) · ×1

Duplicated block (15 lines × 2) quickwit/quickwit-config/src/metastore_config.rs:221 — quickwit/quickwit-config/src/metastore_config.rs:221-235 | quickwit/quickwit-config/src/metastore_config.rs:239-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.

D4 · Code Duplication · Duplicated block (12 lines × 3) · ×1

Duplicated block (12 lines × 3) quickwit/quickwit-indexing/src/source/ingest/mod.rs:480 — quickwit/quickwit-indexing/src/source/ingest/mod.rs:480-491 | quickwit/quickwit-indexing/src/source/kafka_source.rs:483-494 | quickwit/quickwit-indexing/src/source/pulsar_source.rs:241-253 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.

D4 · Code Duplication · Duplicated block (10 lines × 4) · ×1

Duplicated block (10 lines × 4) quickwit/quickwit-proto/src/types/doc_mapping_uid.rs:98 — quickwit/quickwit-proto/src/types/doc_mapping_uid.rs:98-107 | quickwit/quickwit-proto/src/types/doc_uid.rs:97-106 | quickwit/quickwit-proto/src/types/index_uid.rs:136-145 | quickwit/quickwit-proto/src/types/pipeline_uid.rs:101-110 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once.

D5 · Coupling · Unstable project quickwit-compaction · ×1

Unstable project quickwit-compaction — quickwit-compaction has instability 0.83 with 2 dependents.

D5 · Coupling · Unstable project quickwit-control-plane · ×1

Unstable project quickwit-control-plane — quickwit-control-plane has instability 0.89 with 1 dependents.

D5 · Coupling · Unstable project quickwit-jaeger · ×1

Unstable project quickwit-jaeger — quickwit-jaeger has instability 0.88 with 1 dependents.

D5 · Coupling · Unstable project quickwit-janitor · ×1

Unstable project quickwit-janitor — quickwit-janitor has instability 0.93 with 1 dependents.

D5 · Coupling · Unstable project quickwit-lambda-client · ×1

Unstable project quickwit-lambda-client — quickwit-lambda-client has instability 0.86 with 1 dependents.

D5 · Coupling · Unstable project quickwit-lambda-server · ×1

Unstable project quickwit-lambda-server — quickwit-lambda-server has instability 0.86 with 1 dependents.

D5 · Coupling · Unstable project quickwit-rest-client · ×1

Unstable project quickwit-rest-client — quickwit-rest-client has instability 0.89 with 1 dependents.

D5 · Coupling · Unstable project quickwit-serve · ×1

Unstable project quickwit-serve — quickwit-serve has instability 0.92 with 2 dependents.

D8 · Code Coverage · Coverage not measured · ×1

Coverage not measured — JavaScript/TypeScript suite — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the jest suite in quickwit/quickwit-ui/ ran and not one test passed (FAIL src/views/SearchView.test.jsx), so the coverage would describe the failed run, not the code. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.

P12 · CI test-gate honesty · Coverage collected but not gated · ×1

Coverage collected but not gated — CI collects a coverage report but no step enforces a minimum — coverage could halve and CI stays green. Add a step that fails the build when coverage drops below a floor (your coverage tool's minimum-threshold flag, or a coverage-gate action) so the number guards something. What was searched, so you can tell an absence from a miss: this repository's CI files AND its coverage configuration — the well-known coverage and test-runner config files, read at the repository root and inside workspace package directories two levels down, so a floor declared beside the tests rather than in the pipeline is credited — matched against the threshold settings this check knows by name. A floor set in your coverage service's web UI rather than in a committed file, or under a setting whose name is not one of those, is not seen here.

P7 · Outbound HTTP resilience · Outbound HTTP without resilience · ×1

Outbound HTTP without resilience quickwit/quickwit-indexing/src/source/pulsar_source.rs:624 — `reqwest::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.

R10 · Code Duplication · Duplicated block (17 lines × 2 locations) · ×1

Duplicated block (17 lines × 2 locations) quickwit/quickwit-ui/src/components/TimeRangeSelect.tsx:233 — quickwit/quickwit-ui/src/components/TimeRangeSelect.tsx:233 · quickwit/quickwit-ui/src/components/TimeRangeSelect.tsx:252 — 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 (13 lines × 2 locations) · ×1

Duplicated block (13 lines × 2 locations) quickwit/quickwit-ui/src/components/QueryEditor/AggregationEditor.tsx:189 — quickwit/quickwit-ui/src/components/QueryEditor/AggregationEditor.tsx:189 · quickwit/quickwit-ui/src/components/QueryEditor/AggregationEditor.tsx:204 — 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.

R2 · Cyclomatic Complexity · Complex function parseSearchUrl (cyclomatic 11, cognitive 12) · ×1

Complex function parseSearchUrl (cyclomatic 11, cognitive 12) quickwit/quickwit-ui/src/utils/urls.ts:28 — parseSearchUrl has cyclomatic complexity 11 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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.

R7 · Dead Code · Dead file (~54 LoC) · ×1

Dead file (~54 LoC) quickwit/quickwit-ui/src/providers/EditorProvider.tsx — no import path from any entry point (7 application, 3 tooling, 11 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

R8 · Dependency Hygiene · Unused dependency '@emotion/react' · ×1

Unused dependency '@emotion/react' — Declared in quickwit/quickwit-ui/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.

R8 · Dependency Hygiene · Unused dependency '@mui/system' · ×1

Unused dependency '@mui/system' — Declared in quickwit/quickwit-ui/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.

R8 · Dependency Hygiene · Unused dependency '@testing-library/user-event' · ×1

Unused dependency '@testing-library/user-event' — Declared in quickwit/quickwit-ui/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.

Minor — 24 finding(s)

D16 · Bus Factor · Off-boarding risk · ×3

Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 8 significant file(s) lose their only recent owner: quickwit/quickwit-metrics/src/lib.rs, quickwit/quickwit-indexing/src/docs_clustering/fingerprinter.rs, quickwit/quickwit-config/src/docs_clustering.rs, quickwit/quickwit-storage/src/prefix_storage.rs, quickwit/quickwit-metrics/src/inner.rs, quickwit/quickwit-indexing/src/docs_clustering/clusterer.rs, quickwit/quickwit-storage/src/cache/storage_with_cache.rs, quickwit/quickwit-indexing/src/docs_clustering/mod.rs. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 5 significant file(s) lose their only recent owner: quickwit/quickwit-transport/src/tls.rs, quickwit/quickwit-ingest/src/ingest_v2/mrecordlog_utils.rs, quickwit/quickwit-actors/src/registry.rs, quickwit/quickwit-ingest/src/mrecordlog_async.rs, quickwit/scripts/inspect_split.py. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #3 — If anonymized user #3 becomes unavailable, 3 significant file(s) lose their only recent owner: quickwit/quickwit-compaction/src/compaction_pipeline.rs, quickwit/quickwit-config/src/config_value.rs, quickwit/quickwit-compaction/src/lib.rs. Pair on, review, or document these before any departure.

D31 · IaC & Container Security · Low IaC · ×2

REDACTED
REDACTED

D16 · Bus Factor · Further sole-owners (lower concentration) · ×1

Further sole-owners (lower concentration) — 6 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 (23 single-owned of 505 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; 505 of the 621 production source files in this repository met that bar). They are anonymized user #4 (2 file(s)), anonymized user #5 (1 file(s)), anonymized user #6 (1 file(s)), anonymized user #7 (1 file(s)), anonymized user #8 (1 file(s)), anonymized user #9 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above.

D19 · Documentation Quality · Documentation · ×1

Documentation: contradicts the code quickwit/quickwit-metastore/migrations/postgresql_deferred/README.md — The deferred migration doc describes a global versioning rule that is no longer valid because the metastore uses a single SQLx migration table and the PostgreSQL migrations are all sequential. Update the deferred-migration section to reflect the new single-table, sequential model.

D20 · ADR Quality · No ADRs found · ×1

No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.

D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1

Projects may be oversized for their cohesion — 4 of 34 project(s) overshoot their size bounds, lowering Project Cohesion to 7.7/10. The most over is `quickwit/quickwit-indexing` (31738 LoC, 159 public types across 11 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.

D30 · Dependency Vulnerabilities · Low CVE · ×1

REDACTED

D34 · Knowledge Freshness · Further orphaned files (smaller) · ×1

Further orphaned files (smaller) — 21 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: quickwit/quickwit-common/src/alloc_tracker.rs, quickwit/quickwit-serve/src/index_api/source_resource.rs, quickwit/quickwit-indexing/src/source/queue_sources/message.rs, quickwit/quickwit-ingest/src/doc_batch.rs, quickwit/quickwit-ingest/src/ingest_v2/publish_tracker.rs, quickwit/quickwit-common/src/jemalloc_profiled.rs, quickwit/quickwit-serve/src/ingest_api/response.rs, quickwit/quickwit-directories/src/debug_proxy_directory.rs (and 13 more) (24 orphaned of 505 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; 505 of the 621 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.

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

M2 · Architecture documentation · No ADRs · ×1

No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.

P2 · Observability · Logging is not universal · ×1

Logging is not universal — Only 28/30 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `quickwit/quickwit-metastore-utils`, `quickwit/quickwit-metrics-inventory`.

R7 · Dead Code · Unused export 'setErrorMarker' · ×1

Unused export 'setErrorMarker' quickwit/quickwit-ui/src/components/QueryEditor/config.ts:183 — Nothing imports this binding — it is safe to review for removal.

R7 · Dead Code · Unused export 'DATE_TIME_WITH_MILLISECONDS_FORMAT' · ×1

Unused export 'DATE_TIME_WITH_MILLISECONDS_FORMAT' quickwit/quickwit-ui/src/utils/models.ts:43 — Nothing imports this binding — it is safe to review for removal.

R7 · Dead Code · Unused export 'EMPTY_INDEX_METADATA' · ×1

Unused export 'EMPTY_INDEX_METADATA' quickwit/quickwit-ui/src/utils/models.ts:242 — Nothing imports this binding — it is safe to review for removal.

R7 · Dead Code · Unused export 'QUICKWIT_RED' · ×1

Unused export 'QUICKWIT_RED' quickwit/quickwit-ui/src/utils/theme.ts:22 — Nothing imports this binding — it is safe to review for removal.

R7 · Dead Code · Unused export 'QUICKWIT_GREEN' · ×1

Unused export 'QUICKWIT_GREEN' quickwit/quickwit-ui/src/utils/theme.ts:23 — Nothing imports this binding — it is safe to review for removal.

R7 · Dead Code · Unused export 'QUICKWIT_GREY' · ×1

Unused export 'QUICKWIT_GREY' quickwit/quickwit-ui/src/utils/theme.ts:24 — Nothing imports this binding — it is safe to review for removal.

R7 · Dead Code · Unused export 'QUICKWIT_BLACK' · ×1

Unused export 'QUICKWIT_BLACK' quickwit/quickwit-ui/src/utils/theme.ts:27 — Nothing imports this binding — it is safe to review for removal.

R8 · Dependency Hygiene · Test-only dependency '@testing-library/react' in production deps · ×1

Test-only dependency '@testing-library/react' in production deps quickwit/quickwit-ui/src/index.test.js:16 — Only test files import it — move it to devDependencies.

Minor — 2 finding(s)

D12 · Dependency Hygiene · Outdated · ×2

Outdated: glob — `glob` is locked at 0.3.3 but 0.3.4 is the current stable release on crates.io, and it already satisfies the `"0.3"` requirement declared in quickwit/quickwit-proto/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p glob` and commit the updated REDACTED.
Outdated: serde — `serde` is locked at 1.0.228 but 1.0.229 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in quickwit/quickwit-metastore-utils/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p serde` and commit the updated REDACTED.

Appendix B — Reproduction & audit trail

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

Dimension	Tool	Version	Command	Findings	Raw output
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-ac861dc3ec274a38aa0dff36dca1421f/history.json --exit-code 0 --source .	1	artifacts/raw/gitleaks-history.json
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-ac861dc3ec274a38aa0dff36dca1421f/tree.json --exit-code 0 --source .	0	artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)	semgrep	—	semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off .	36	artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilities	trivy	—	trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs /bin/ --skip-dirs /obj/ . --skip-db-update	28	artifacts/raw/trivy-fs.json
D31 · IaC & Container Security	trivy	—	trivy config --format json --quiet .	32	artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)	semgrep	—	semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 1 file(s) — `quickwit/quickwit-ui/vite.config.ts` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.	0	—
D40 · Network Egress Confinement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.	0	—
D41 · Kernel & Syscall Confinement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.	0	—
D42 · Runtime Threat Enforcement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.	0	—
D43 · Malicious Dependencies	trivy	—	trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs /bin/ --skip-dirs /obj/ . --skip-db-update	0	artifacts/raw/trivy-fs.json

Run 01a0eaf6-5b61-7fe4-aed8-2a512c367cf6 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Quickwit-Oss/quickwit

Findings by grade

This survey was produced by

Executive summary

Top priorities

Diagnosis — what's actually going on

Architecture — module dependency graph

Architecture — module dependency matrix

At a glance — Code Health · 88% · Exemplary ·

At a glance — Architecture · 93% · Exemplary ·

At a glance — Maturity · 78% · Strong ·

At a glance — Readiness · 67% · Adequate · gated by P7 ·

At a glance — Security · 52% · Adequate · gated by D29, D30, D31, D36 ·

At a glance — Domain Modelling · 86% · Exemplary ·

At a glance — Event Sourcing · 100% · Exemplary ·

At a glance — Accessibility · 71% · Strong ·

At a glance — Performance · 60% · Adequate ·

Security & Compliance — OWASP Top-10 mapping

Roadmap

File quality

How the grades work

Methodology & how to trust this report

Tools & methods

Run transparency — what happened this run

Limitations & what we did not check

Per-dimension blind spots

The LLM boundary

Dimensions

Frontend & cross-cutting dimensions

WCAG coverage — what static analysis assessed

Reference — by lens

Appendix A — Findings (grouped)

Appendix B — Reproduction & audit trail

Downloadable artifacts