Public report of milvus-io/milvus, published 24 October 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive report Measured under the Code Assurance Index, an open standard. This copy doesn't carry the survey's signed record. How a survey is checked →

milvus-io/milvus

Measured 24 October 2026, 02:48 UTC, at code version 78f1a7a

Regression: 1 dimension fell since the last survey Test reliability: not measured

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

Test reliability is not measured: The suite could not be re-run, but the repository declares tests of its own unreliable.

CAI score 52out of 100 Adequate
CriticalWeakAdequateStrongExemplary
Down 4 since the last survey

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

Architecture 100 Exemplary Code Health 91 Exemplary Performance 88 Exemplary Maturity 84 Exemplary Production Readiness 55 Adequate Accessibility 49 Adequate Security and Compliance 41 Weak

A very large codebase: 565,420 lines of product code in 8 projects, tests not counted · Estimated rebuild effort: about 11.3 person-years · Weakest lens: Security and Compliance, 41

Findings by how serious they are

272 critical 871 serious 917 minor

21 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.

This survey was produced by

Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
24 October 2026, 02:48 UTC

A measurement, not a certificate. The Code Assurance Index records a number together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee the code. The standard was written by Canine Development, which also builds Watchdog. It is open to any tool that implements it, and today Watchdog is the only one that does.

The score is deterministic, which means the same code always gets the same score. Watchdog works it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸

65of 71 dimensions measured by tools. The other 6 are advisory notes from an AI model, which explain the code but don't count towards the score.
1916of 2060 findings point to an exact file and line, so you can open each one in the code. The other 144 concern the repository as a whole, such as missing documentation.
71dimensions across 7 lenses, read from 565,420 lines of product code in 8 projects.
Chapters

Executive summary

milvus-io/milvus scores 52 out of 100 and is rated Adequate, while five of its seven lenses score higher still: Architecture at 100, Code Health at 91, Performance at 88 and Maturity at 84, all rated Exemplary, and Production Readiness at 55, rated Adequate. Watchdog judged it as a template, sample or demo, meant to be read or copied, so the dimensions about building, releasing and running a product don't apply, and its lenses are rated against a lower bar. The score itself is worked out as for any repository.

The score is lower than those five because the weakest lens counts most, and here that is Security and Compliance, which scores 41 and is rated Weak. Its Secrets (history) dimension scores 0 out of 10, and until that reaches 4, Security and Compliance can't be rated higher than Adequate. The first actions are to resolve the 6 Leaked secret finding(s) in REDACTED Scanning and to resolve the 2 Dependency pinned to a stale untagged commit finding(s) in Dependency Hygiene, and if Security and Compliance rose to 70, the score would rise from 52 to about 60.

272 findings are critical: 150 in Static Analysis (SAST), 76 in IaC & Container Security, 14 in Forms & labels, 14 in Secrets (history), six in REDACTED Scanning, four in Test Reliability, three in Dependency Vulnerabilities, two in Knowledge Freshness, one in ADR Conformance, one in Change Coupling and one in Keyboard semantics.

Watchdog couldn't measure 21 dimensions in this code, among them Cyclomatic Complexity, Cognitive Complexity and Code Coverage, so they are left out of the score. The product code is 565,420 lines, which would take an estimated 11.3 person-years, around €1,600,000, to rebuild.

Code Health 91 ★ Exemplary Architecture 100 ★ Exemplary Maturity 84 ★ Exemplary Production Readiness 55 Adequate, capped by REDACTED Scanning and Outbound HTTP resilience Security and Compliance 41 Weak, capped by Secrets (history), Static Analysis (SAST), Dependency Vulnerabilities, IaC & Container Security and Supply-chain Provenance & Signing Accessibility 49 Adequate Performance 88 ★ Exemplary

A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Security and Compliance 41 · counts for 46%Accessibility 49 · counts for 25%Production Readiness 55 · counts for 14%Maturity 84 · counts for 8%Performance 88 · counts for 4%Code Health 91 · counts for 2%Architecture 100 · counts for 1%

If Security and Compliance rose from 41 to 70, the lowest score rated Strong, the score would rise from 52 to about 60.

Code composition: what the lines of code are
Product code 33%Tests 67%
New since the last survey: 123 findings

These 123 critical or serious findings weren't in the previous survey, on 10 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.

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

Fixed since the last survey: 373 findings

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

  • Explicit Debt · TodoComment internal/datacoord/handler.go
  • Explicit Debt · TodoComment internal/datacoord/ddl_callbacks_import.go
  • Explicit Debt · TodoComment internal/metastore/kv/rootcoord/kv_catalog.go
  • Explicit Debt · TodoComment internal/metastore/kv/rootcoord/kv_catalog.go
  • Explicit Debt · TodoComment REDACTED
  • Explicit Debt · TodoComment REDACTED
  • Explicit Debt · TodoComment internal/proxy/task_test.go
  • Explicit Debt · TodoComment internal/proxy/task_index.go
  • Explicit Debt · TodoComment internal/proxy/task_index.go
  • Explicit Debt · TodoComment internal/proxy/task_index.go
  • Explicit Debt · TodoComment REDACTED
  • Explicit Debt · TodoComment internal/querynodev2/tasks/search_task.go
  • Explicit Debt · TodoComment internal/querynodev2/tasks/query_task.go
  • Explicit Debt · TodoComment internal/rootcoord/meta_table.go
  • Explicit Debt · TodoComment internal/rootcoord/meta_table.go
  • Explicit Debt · TodoComment internal/streamingnode/server/wal/interceptors/redo/redo_interceptor.go
  • Explicit Debt · TodoComment internal/streamingnode/server/wal/interceptors/redo/redo_interceptor.go
  • Explicit Debt · TodoComment internal/util/indexcgowrapper/index_test.go
  • Explicit Debt · TodoComment internal/util/indexcgowrapper/index_bench.go
  • Explicit Debt · TodoComment REDACTED
  • Explicit Debt · TodoComment REDACTED
  • Explicit Debt · TodoComment REDACTED
  • Explicit Debt · TodoComment REDACTED
  • Explicit Debt · TodoComment internal/util/indexcgowrapper/dataset.go
  • Static Analysis (SAST) · Medium: REDACTED internal/util/testutil/test_util.go
  • Dependency Vulnerabilities · Medium CVE: GO-2026-6599 REDACTED
  • Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium CVE: GO-2026-6505 REDACTED
  • Dependency Vulnerabilities · Medium CVE: GO-2026-6505 REDACTED
  • Dependency Vulnerabilities · Medium CVE: GO-2026-6505 REDACTED
  • Dependency Vulnerabilities · Medium CVE: GO-2026-6505 REDACTED
  • Dependency Vulnerabilities · Medium CVE: GO-2026-6599 REDACTED
  • Dependency Vulnerabilities · Medium advisory (unsound): REDACTED REDACTED
  • IaC & Container Security · Medium IaC: CKV2_K8S_6 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_15 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_20 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_22 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_23 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_28 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_29 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_30 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_31 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_37 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_38 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_40 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_43 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_8 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_9 REDACTED
  • IaC & Container Security · Medium IaC: CKV2_K8S_6 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_10 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_11 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_12 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_13 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_14 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_15 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_20 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_22 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_23 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_28 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_29 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_30 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_31 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_37 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_38 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_40 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_43 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_8 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_9 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_32 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_2 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_24 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_32 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_4 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_6 REDACTED
  • IaC & Container Security · Medium IaC: CKV2_K8S_6 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_23 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_25 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_29 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_31 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_35 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_38 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_39 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_40 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_43 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_8 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_9 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_19 REDACTED
  • IaC & Container Security · Medium IaC: CKV2_K8S_6 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_31 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_38 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_43 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_8 REDACTED
  • IaC & Container Security · Medium IaC: CKV_K8S_9 REDACTED
  • IaC & Container Security · Medium IaC: REDACTED REDACTED
  • IaC & Container Security · Medium IaC: REDACTED REDACTED
  • IaC & Container Security · Medium IaC: REDACTED REDACTED
  • IaC & Container Security · Medium IaC: REDACTED REDACTED
  • IaC & Container Security · Medium IaC: REDACTED REDACTED
  • IaC & Container Security · Medium IaC: REDACTED REDACTED
  • IaC & Container Security · Medium IaC: CKV2_DOCKER_17 REDACTED
Rebuild cost: about €1,600,000 · Estimate
Cost to rebuild€550,000 to €2,700,000, for 9,103 to 28,879 hours of work, about 11.3 person-years for 6 to 22 engineers
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.7 at a score of 52. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
SizeVery large: 565,420 lines of product code

How the estimate is made: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.

Top priorities

The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.

1
Resolve the 6 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED, REDACTED.
Raises the score by about 5 points · Low effort · REDACTED Scanning
2
Resolve the 2 Dependency pinned to a stale untagged commit finding(s) in Dependency Hygiene.
Raises the score by about 3 points · Low effort · Dependency Hygiene
3
Resolve the 12 High secret finding(s) in Secrets (history) — start with REDACTED (9), REDACTED (3).
Raises the score by about 4 points · Medium effort · Secrets (history)

Diagnosis: what the measurements show together

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

Where the investment is most exposed · Value at risk
This code would cost about €1,600,000 to build again, about 11.3 person-years of work. Its weakest lens is Security and Compliance, at 41 (Weak). Security and Compliance is about how well the product is protected, and how it handles personal data. Because the weakest lens counts most in the score, work on Security and Compliance also moves the score most.
Based on: the rebuild estimate · the Security and Compliance grade · how much each lens counts
What to do: Start with the Security and Compliance actions in Top priorities.
If you do one thing first · First action
Resolve the 6 Leaked secret finding(s) in REDACTED Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 5 points for low effort, because it clears the 6 REDACTED Scanning findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort

Architecture — module dependency graph

Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways — a layering smell or cycle. A clean layered graph has none.

arch gcp-native-storage gcp-native-storage github.com/milvus-io/milvus milvus github.com/milvus-io/milvus/client/v3 v3 github.com/milvus-io/milvus->github.com/milvus-io/milvus/client/v3 github.com/milvus-io/milvus/pkg/v3 v3 github.com/milvus-io/milvus->github.com/milvus-io/milvus/pkg/v3 milvus-pyudf-runtime milvus-pyudf-runtime milvus_bitset milvus_bitset milvus_minhash milvus_minhash tantivy-binding tantivy-binding

Architecture: which parts of the code depend on which

The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.

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

The table shows the 40 modules with the most connections; 145 more are left out to keep it readable.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 internal.util.function.pyudf.python.milvus_pyudf_runtime.config2 internal.util.function.pyudf.python.milvus_pyudf_runtime.instance3 internal.util.function.pyudf.python.milvus_pyudf_runtime.proto.pyudf_pb2_grpc4 tantivy_binding5 tantivy_binding.analyzer.dict.lindera.fetch6 tantivy_binding.analyzer.gen.milvus.proto.tokenizer.tokenization_request7 tantivy_binding.bitset_wrapper8 tantivy_binding.data_type9 tantivy_binding.error10 tests.python_client.base.client_base11 internal.util.function.pyudf.python.milvus_pyudf_runtime12 internal.util.function.pyudf.python.milvus_pyudf_runtime.loader13 internal.util.function.pyudf.python.milvus_pyudf_runtime.supervisor14 internal.util.function.pyudf.python.milvus_pyudf_runtime.worker15 tantivy_binding.analyzer.dict.lindera.cc_cedict16 tantivy_binding.analyzer.dict.lindera.ipadic17 tantivy_binding.analyzer.dict.lindera.ipadic_neologd18 tantivy_binding.analyzer.gen.milvus.proto.tokenizer19 tantivy_binding.index_writer20 tantivy_binding.analyzer.tokenizers.grpc_tokenizer21 tantivy_binding.array22 tantivy_binding.analyzer.char_filter23 tantivy_binding.analyzer.char_filter.char_filter24 tantivy_binding.analyzer.options.resource_info25 tantivy_binding.index_reader_c26 tantivy_binding.index_writer_c27 tantivy_binding.analyzer.analyzer28 tantivy_binding.analyzer.build_in_analyzer29 tantivy_binding.analyzer.char_filter.mapping_char_filter30 tantivy_binding.analyzer.filter.filter31 tantivy_binding.analyzer.filter.synonym_filter32 tantivy_binding.analyzer.filter.util33 tantivy_binding.analyzer.options.runtime_option34 tantivy_binding.analyzer.options.util35 tantivy_binding.analyzer.tokenizers.char_filter_tokenizer36 tantivy_binding.analyzer.tokenizers.jieba_tokenizer37 tantivy_binding.analyzer.tokenizers.lang_ident_tokenizer38 tantivy_binding.analyzer.tokenizers.lindera_tokenizer39 tantivy_binding.analyzer.tokenizers.tokenizer40 tantivy_binding.analyzer.filter.stemmer_filter
1 internal.util.function.pyudf.python.milvus_pyudf_runtime.config
2 internal.util.function.pyudf.python.milvus_pyudf_runtime.instance
3 internal.util.function.pyudf.python.milvus_pyudf_runtime.proto.pyudf_pb2_grpc
4 tantivy_binding
5 tantivy_binding.analyzer.dict.lindera.fetch
6 tantivy_binding.analyzer.gen.milvus.proto.tokenizer.tokenization_request
7 tantivy_binding.bitset_wrapper
8 tantivy_binding.data_type
9 tantivy_binding.error
10 tests.python_client.base.client_base
11 internal.util.function.pyudf.python.milvus_pyudf_runtime1
12 internal.util.function.pyudf.python.milvus_pyudf_runtime.loader1
13 internal.util.function.pyudf.python.milvus_pyudf_runtime.supervisor1
14 internal.util.function.pyudf.python.milvus_pyudf_runtime.worker11
15 tantivy_binding.analyzer.dict.lindera.cc_cedict1
16 tantivy_binding.analyzer.dict.lindera.ipadic1
17 tantivy_binding.analyzer.dict.lindera.ipadic_neologd1
18 tantivy_binding.analyzer.gen.milvus.proto.tokenizer1
19 tantivy_binding.index_writer11
20 tantivy_binding.analyzer.tokenizers.grpc_tokenizer12
21 tantivy_binding.array21
22 tantivy_binding.analyzer.char_filter1
23 tantivy_binding.analyzer.char_filter.char_filter1
24 tantivy_binding.analyzer.options.resource_info2
25 tantivy_binding.index_reader_c11
26 tantivy_binding.index_writer_c111
27 tantivy_binding.analyzer.analyzer12
28 tantivy_binding.analyzer.build_in_analyzer1
29 tantivy_binding.analyzer.char_filter.mapping_char_filter12
30 tantivy_binding.analyzer.filter.filter2
31 tantivy_binding.analyzer.filter.synonym_filter11
32 tantivy_binding.analyzer.filter.util11
33 tantivy_binding.analyzer.options.runtime_option33
34 tantivy_binding.analyzer.options.util11
35 tantivy_binding.analyzer.tokenizers.char_filter_tokenizer13
36 tantivy_binding.analyzer.tokenizers.jieba_tokenizer22
37 tantivy_binding.analyzer.tokenizers.lang_ident_tokenizer11
38 tantivy_binding.analyzer.tokenizers.lindera_tokenizer212
39 tantivy_binding.analyzer.tokenizers.tokenizer11
40 tantivy_binding.analyzer.filter.stemmer_filter111
Uses a module listed above itPart of a loopThe module itself
1 internal.util.function.pyudf.python.milvus_pyudf_runtime.config2 internal.util.function.pyudf.python.milvus_pyudf_runtime.instance3 internal.util.function.pyudf.python.milvus_pyudf_runtime.proto.pyudf_pb2_grpc4 tantivy_binding5 tantivy_binding.analyzer.dict.lindera.fetch6 tantivy_binding.analyzer.gen.milvus.proto.tokenizer.tokenization_request7 tantivy_binding.bitset_wrapper8 tantivy_binding.data_type9 tantivy_binding.error10 tests.python_client.base.client_base11 internal.util.function.pyudf.python.milvus_pyudf_runtime12 internal.util.function.pyudf.python.milvus_pyudf_runtime.loader13 internal.util.function.pyudf.python.milvus_pyudf_runtime.supervisor14 internal.util.function.pyudf.python.milvus_pyudf_runtime.worker15 tantivy_binding.analyzer.dict.lindera.cc_cedict16 tantivy_binding.analyzer.dict.lindera.ipadic17 tantivy_binding.analyzer.dict.lindera.ipadic_neologd18 tantivy_binding.analyzer.gen.milvus.proto.tokenizer19 tantivy_binding.index_writer20 tantivy_binding.analyzer.tokenizers.grpc_tokenizer21 tantivy_binding.array22 tantivy_binding.analyzer.char_filter23 tantivy_binding.analyzer.char_filter.char_filter24 tantivy_binding.analyzer.options.resource_info25 tantivy_binding.index_reader_c26 tantivy_binding.index_writer_c27 tantivy_binding.analyzer.analyzer28 tantivy_binding.analyzer.build_in_analyzer29 tantivy_binding.analyzer.char_filter.mapping_char_filter30 tantivy_binding.analyzer.filter.filter31 tantivy_binding.analyzer.filter.synonym_filter32 tantivy_binding.analyzer.filter.util33 tantivy_binding.analyzer.options.runtime_option34 tantivy_binding.analyzer.options.util35 tantivy_binding.analyzer.tokenizers.char_filter_tokenizer36 tantivy_binding.analyzer.tokenizers.jieba_tokenizer37 tantivy_binding.analyzer.tokenizers.lang_ident_tokenizer38 tantivy_binding.analyzer.tokenizers.lindera_tokenizer39 tantivy_binding.analyzer.tokenizers.tokenizer40 tantivy_binding.analyzer.filter.stemmer_filterinternal.util.function.pyudf.python.milvus_pyudf_runtime.config1internal.util.function.pyudf.python.milvus_pyudf_runtime.instance2internal.util.function.pyudf.python.milvus_pyudf_runtime.proto.pyudf_pb2_grpc3tantivy_binding4tantivy_binding.analyzer.dict.lindera.fetch5tantivy_binding.analyzer.gen.milvus.proto.tokenizer.tokenization_request6tantivy_binding.bitset_wrapper7tantivy_binding.data_type8tantivy_binding.error9tests.python_client.base.client_base10internal.util.function.pyudf.python.milvus_pyudf_runtime11internal.util.function.pyudf.python.milvus_pyudf_runtime.loader12internal.util.function.pyudf.python.milvus_pyudf_runtime.supervisor13internal.util.function.pyudf.python.milvus_pyudf_runtime.worker14tantivy_binding.analyzer.dict.lindera.cc_cedict15tantivy_binding.analyzer.dict.lindera.ipadic16tantivy_binding.analyzer.dict.lindera.ipadic_neologd17tantivy_binding.analyzer.gen.milvus.proto.tokenizer18tantivy_binding.index_writer19tantivy_binding.analyzer.tokenizers.grpc_tokenizer20tantivy_binding.array21tantivy_binding.analyzer.char_filter22tantivy_binding.analyzer.char_filter.char_filter23tantivy_binding.analyzer.options.resource_info24tantivy_binding.index_reader_c25tantivy_binding.index_writer_c26tantivy_binding.analyzer.analyzer27tantivy_binding.analyzer.build_in_analyzer28tantivy_binding.analyzer.char_filter.mapping_char_filter29tantivy_binding.analyzer.filter.filter30tantivy_binding.analyzer.filter.synonym_filter31tantivy_binding.analyzer.filter.util32tantivy_binding.analyzer.options.runtime_option33tantivy_binding.analyzer.options.util34tantivy_binding.analyzer.tokenizers.char_filter_tokenizer35tantivy_binding.analyzer.tokenizers.jieba_tokenizer36tantivy_binding.analyzer.tokenizers.lang_ident_tokenizer37tantivy_binding.analyzer.tokenizers.lindera_tokenizer38tantivy_binding.analyzer.tokenizers.tokenizer39tantivy_binding.analyzer.filter.stemmer_filter40111111111111221112111111211221111331113221121211111+145 more modules (most-connected shown)

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

The Good
D4 · Python Code Duplication 10.0 D17 · Python Explicit Debt 9.8 X1 · Repo Async correctness 10.0 X12 · Repo Unreachable branch 8.0 X13 · Repo Undrained process stream 10.0 X19 · Repo Unrestored process-global state 10.0 X2 · Repo Cancellation propagation 9.3 X21 · Repo Side-effecting pattern guard 10.0 X22 · Repo Contradicted release guard 10.0 X23 · Repo Unguarded diagnostic materialisation 10.0 X25 · Repo Inert configuration knob 10.0 X26 · Repo Unsynchronised callback handoff 10.0 X27 · Repo Collection changed while being enumerated 10.0 X28 · Repo Index access outside its own emptiness guard 10.0 X3 · Repo Exception handling 7.6 X30 · Repo Support guard that admits what it rejects 10.0 X4 · Repo Structured logging 10.0

At a glance — Architecture · 100% · Exemplary ·

The Good
D5 · Python Coupling 10.0 D6 · Python Cohesion (LCOM4) 9.8 D7 · Python Architectural Integrity 10.0 D35 · Python Change Coupling 10.0 AX10 · Repo Code composition 9.9 AX3 · Repo Project dependency cycles 10.0 AX4 · Repo Dependency direction 10.0 AX8 · Repo Test isolation 10.0 AX9 · Repo CQS / query purity 10.0
The Ugly
D22 · Python Internal API Consistency 4.0

At a glance — Maturity · 84% · Exemplary ·

The Good
D16 · Python Bus Factor 9.4 D19 · Python Documentation Quality 8.4 D20 · Python ADR Quality 8.5 D21 · Python Naming Consistency 10.0 D25 · Python ADR Conformance 9.4 D34 · Python Knowledge Freshness 9.6 M1 · Repo Documentation (README) 7.3 M2 · Repo Architecture documentation 10.0 M3 · Repo Folder & project structure 10.0 M4 · Repo Documentation accuracy 7.6

At a glance — Readiness · 55% · Adequate · gated by D13, P7 ·

The Good
D9 · Python Test Distribution 10.0 D12 · Python Dependency Hygiene 6.9 D14 · Python License Compliance 10.0 P1 · Repo CI/CD gates 10.0 P10 · Repo Library API & versioning 10.0 P2 · Repo Observability 9.1 P3 · Repo Security & performance tooling 6.0 P4 · Repo Deployment & Rollback 10.0 P5 · Repo DR & Backup 7.0
The Bad
P6 · Repo Release Hygiene 5.0
The Ugly
D13 · Python REDACTED Scanning 0.0 P7 · Repo Outbound HTTP resilience 3.0

At a glance — Security · 41% · Weak · gated by D28, D29, D30, D31, D36 ·

The Good
D43 · Python Malicious Dependencies 10.0 D44 · Python Platform End-of-Life 10.0 X14 · Repo Bypassable address classification 10.0 X15 · Repo Unvalidated length from an untrusted reader 10.0 X17 · Repo Uncapped recursion over a caller-supplied document 10.0 X24 · Repo Document value interpolated into markup unescaped 10.0
The Bad
D40 · Python Network Egress Confinement 6.0 D41 · Python Kernel & Syscall Confinement 6.0 D42 · Python Runtime Threat Enforcement 6.0
The Ugly
D28 · Python Secrets (history) 0.0 D29 · Python Static Analysis (SAST) 0.0 D30 · Python Dependency Vulnerabilities 2.9 D31 · Python IaC & Container Security 0.0 D36 · Python Supply-chain Provenance & Signing 0.0

At a glance — Accessibility · 49% · Adequate ·

The Good
AC3 · Repo Page structure 10.0
The Bad
AC2 · Repo Forms & labels 4.2 AC4 · Repo Keyboard semantics 5.0 AC6 · Repo Visual & motion safety 4.6 AC7 · Repo A11y enforcement 4.0

At a glance — Performance · 88% · Exemplary ·

The Good
PF1 · Repo Benchmark discipline 9.5 PF2 · Repo Allocation hygiene 7.7 PF3 · Repo Async & latency hygiene 10.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 categoryFindingsSeverity
A05:2025 — Injection729High / Critical
A02:2025 — Security Misconfiguration253High / Critical
A03:2025 — Software Supply Chain Failures57High / Critical
A07:2025 — Authentication Failures21High / Critical

Roadmap

Immediately address security risks by resolving six leaked secrets in source files and twelve historical secrets in build scripts. Strengthen infrastructure integrity by pinning stale dependencies and remediating 128 medium-severity issues in Docker and CI configurations. Finally, enforce accessibility standards by integrating automated checks into the existing test suite to block regressions in CI.

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

Do thisHelpsEffortDimension
Resolve the 6 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED, REDACTED.+4.6 ptsLowREDACTED Scanning
Resolve the 2 Dependency pinned to a stale untagged commit finding(s) in Dependency Hygiene.+2.7 ptsLowDependency Hygiene
Resolve the 12 High secret finding(s) in Secrets (history) — start with REDACTED (9), REDACTED (3).+3.7 ptsMediumSecrets (history)
Resolve the 1 No network policy finding(s) in Network Egress Confinement.+1.8 ptsLowNetwork Egress Confinement
Resolve the 1 Deprecated module finding(s) in Dependency Hygiene.+1.4 ptsLowDependency Hygiene
Enforce accessibility in the test suite you already have: assert the accessibility invariants over the HTML your app renders — parse the rendered output in an existing test, or drive a real browser from one — and gate that test in CI so a regression blocks the merge.+2.0 ptsMediumA11y enforcement
Resolve the 11 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED.+1.9 ptsMediumSupply-chain Provenance & Signing
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.+1.9 ptsMediumForms & labels

File quality

Per-file score 0–10 — a quality signature. Of 575 files carrying findings, judged against the Template bar: 5% slop · 8% mixed · 87% near-clean.

FileScoreBandWorst signal
REDACTED0.0SlopIaC & Container Security: High IaC: REDACTED
REDACTED0.0SlopIaC & Container Security: High IaC: REDACTED
REDACTED0.0SlopIaC & Container Security: High IaC: REDACTED
REDACTED0.0SlopIaC & Container Security: High IaC: REDACTED
REDACTED0.0SlopIaC & Container Security: High IaC: REDACTED
REDACTED0.0SlopIaC & Container Security: High IaC: REDACTED
REDACTED0.0SlopIaC & Container Security: High IaC: REDACTED
REDACTED0.4SlopIaC & Container Security: High IaC: REDACTED
REDACTED0.4SlopIaC & Container Security: High IaC: REDACTED
REDACTED0.4SlopIaC & Container Security: High IaC: REDACTED
REDACTED0.6SlopIaC & Container Security: High IaC: REDACTED
REDACTED0.7SlopIaC & Container Security: High IaC: REDACTED
REDACTED0.8SlopIaC & Container Security: High IaC: REDACTED
REDACTED0.9SlopDependency Vulnerabilities: High CVE: REDACTED
REDACTED0.9SlopIaC & Container Security: High IaC: REDACTED
REDACTED1.4SlopStatic Analysis (SAST): High: REDACTED
REDACTED1.4SlopStatic Analysis (SAST): High: REDACTED
REDACTED1.4SlopStatic Analysis (SAST): High: REDACTED
REDACTED1.4SlopStatic Analysis (SAST): High: REDACTED
REDACTED1.4SlopIaC & Container Security: High IaC: REDACTED

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

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

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

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

Could not be resolved — 21

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. 65 of 71 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 6 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 — 71 dimensions across the health lenses
D4D5D6D7D9D12D13D14D16D17D19D20D21D22D25D28D29D30D31D34D35D36D40D41D42D43D44AC2AC3AC4AC6AC7AX10AX3AX4AX8AX9M1M2M3M4P1P10P2P3P4P5P6P7PF1PF2PF3X1X12X13X14X15X17X19X2X21X22X23X24X25X26X27X28X3X30X4

Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.

How to trust any code-health report — three questions
  1. Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 1916 of 2060 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
  2. Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
  3. Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.

This report answers yes to all three. That's the bar to hold any assessment to.

Tools & methods

The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.

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

Every finding is locatable in findings.md. Run 01a16bcf-81f3-7fa0-a3a1-9cabcaccfebb.

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.

  • D1 Cyclomatic Complexity — 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. Most of this repository's production source (.c, .cpp, .go, .groovy) had no cyclomatic complexity computed for it: no method bodies were exposed for those file kinds by any language model this pass could load.
  • D2 Cognitive Complexity — 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. Most of this repository's production source (.c, .cpp, .go, .groovy) had no cognitive complexity computed for it: no method bodies were exposed for those file kinds by any language model this pass could load.
  • D4 Code Duplication — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 31 duplicated block group(s) on this row were found in the languages this pass could tokenize, and they do NOT cover all of this repository's production source: .go (549,934 lines, 64% of production source), .cpp (189,888 lines, 22% of production source), .c (107,525 lines, 12% of production source) went unread, because no language model this pass could load exposed a clone-unit token stream for those file kinds. Duplication in that source is UNMEASURED — its absence from the count above is a gap in this analyzer's language coverage, not a finding that the code is free of duplication.
  • D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT READ here — but this repository measures it: a Codecov configuration (codecov.yml, target 77%) and a coverage step in CI (`codecov/codecov-action`) shows that coverage is collected and tracked in your own CI. The built-in collector has no runner for this ecosystem (.go, .py), so the analyzer could not read the number — a gap in the analyzer's language coverage, not an unmeasured repo. Not scored. To have the real number read, produce a coverage report in a standard format (`go test -coverprofile=coverage.out ./...`, or `coverage run -m pytest` then `coverage xml`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (`go test -coverprofile=coverage.out ./...`, or `coverage run -m pytest` then `coverage xml`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
  • D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository declares 4 of its own test(s) unreliable. The built-in reliability runner does not support this repository's ecosystem (.go, .py), so the suite was not re-run and no reliability score is given — these are the repository's own declarations, not our measurement.
  • D14 License Compliance — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Go module (REDACTED/go.sum), but the licence verdict published here was taken over its crate dependencies. Nothing was read about its Go dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
  • D15 Churn × Complexity Hotspots — 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. A hotspot is churn × complexity. Churn was measured (998452 line(s) across the 90-day window), but no complexity could be computed for .c, .cpp, .go, .groovy, which is most of this repository's production code — so every churned file would score as complexity 0 and the hotspot list would be empty no matter how tangled the code is. Not scored — this is a gap in the analysis run, not a finding about this repository.
  • D26 Project Cohesion — 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. Project size and spread are measured over build units (a .NET project, a Maven or Gradle module, an npm, Deno or JSR package, a Go module, a Cargo crate, a Python, Composer, Bundler, RubyGems, Mix, rebar3, sbt, SwiftPM or pub package, an OTP application, an Xcode project or XcodeGen spec, or a checkout that declares no build at all) whose source a code model reads. This repository's production source is in a language no model reads, or in units whose build tool D26 does not recognise. That is a gap in this analyzer's language reach — not a finding that the repository's projects are cohesive.
  • D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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.
  • D31 IaC & Container Security — 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. Checkov ran but its report could not be read (checkov produced no output — not a clean result). Every misconfiguration only checkov reports — most of its Terraform, CloudFormation, Bicep and Ansible policies — is absent from this card, so its absence here is not evidence those resources are configured correctly.
  • 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. `client/column/array.go`, `client/column/columns.go`, `client/column/geometry.go`, `client/column/json.go`, `client/column/scalar.go`, … (+24 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
  • AX1 Captive dependencies — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository defines its own container in internal/flushcommon/syncmgr/growing_source.go, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • 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.
  • AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 18 — an image could not be pulled) — pulsar Error Get "https://registry-1.docker.io/v2/": Forbidden gcpnative Error Get "https://registry-1.docker.io/v2/": Forbidden minio Error context canceled etcd Error context canceled gpubuilder Warning context canceled azurite Error context canceled builder Warning context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: gpubuilder Warning context canceled pulsar Error context canceled azurite Error context canceled gcpnative Error context canceled minio Error context canceled jaeger Error context canceled WARNING: Some service image(s) must be built from source by running: docker compose build builder gpubuilder Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped.
  • C1 Data Protection — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
  • 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.
  • GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Go, Python, c, cpp, groovy is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Go, Python, c, cpp, groovy is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 74 further occurrence(s) are not listed individually; the score already reflects all 114.
  • 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.
  • 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 reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in 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.
  • 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 reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in 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.
  • 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 reads C# syntax, and JavaScript/TypeScript, Java, Rust, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, Rust, Dart, Ruby, Scala or Kotlin was found in 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.
  • X3 Exception handling — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 158 further occurrence(s) are not listed individually; the score already reflects all 198.
  • 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 reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's C, Cpp, Groovy, Python is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • Production source was not modelled — run is Degraded — No code model read .c, .cpp, .go, .groovy, so the complexity, duplication and architecture dimensions were scored over a minority of this repository rather than its product, and dimensions that abstained did so for want of a model rather than for want of findings. The grade is NOT representative of this repository; diagnostics.md records the exact cause. The Go sidecar EXITED with code 137 after 24.6s, so the Go code model degraded to null. This is the sidecar's own failure, not a budget of ours. Code 137 is 128+a fatal signal (SIGKILL — under a memory cap this is the cgroup OOM-killer), so it was killed rather than choosing to exit: the same Go source may model cleanly with a larger memory cap.

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

Limitations & what we did not check

Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.

Per-dimension blind spots

For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.

  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
  • D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
  • D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
  • D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • 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.
  • D25 ADR Conformance: ADR conformance is the LLM-scored fraction of sampled code that follows recorded decisions — it checks the decisions that were written down and the slices it sampled, not unrecorded rules or the whole tree.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D40 Network Egress Confinement: Egress confinement is read from committed Kubernetes manifests — a policy applied out-of-band (cluster-default deny, a service mesh, or a cloud firewall/security group off-repo) is invisible, and a present NetworkPolicy is declared config, not proof the cluster admission-controller actually enforces it at runtime.
  • D41 Kernel & Syscall Confinement: Syscall/MAC confinement is read from committed manifests — a profile applied by a cluster-wide PodSecurity default or a mutating webhook off-repo isn't seen, and a declared seccomp/AppArmor profile is config presence, not proof the node's kernel actually loaded and enforced it.
  • D42 Runtime Threat Enforcement: Runtime enforcement is read from committed policy files — a Tetragon/Falco/Kyverno stack installed cluster-wide (Helm release, platform add-on) with no in-repo trace can't be credited, and a committed policy is declared intent, not proof the engine is running and blocking in the live cluster.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (REDACTED, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
  • AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
  • AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
  • AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
  • AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
  • M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • 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 (6): D19, D20, D21, D22, D25, 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

D4 · Code Duplication10.0 / 10Stronggated by 34 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 10.0 / 10 · rule-coverage 100% · ceiling Verified

31 duplicated block group(s) detected. A further 3 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. Measured on part of this repository only: .go, .cpp, .c (98% of production source) was not exposed to the token comparison, so duplication there is unmeasured and is not in this count.

Duplicated block (12 lines × 2) · ×3tools/mgit.py:951
Duplicated block (7 lines × 2) · ×2cmd/tools/binlogv2/minio_client.py:596
Near-duplicate member pair (107 shared lines)cmd/tools/binlogv2/minio_client.py:528
Near-duplicate member pair (46 shared lines)tools/mgit.py:942
Members sharing a duplicated core (5 members, 50+ identical tokens)cmd/tools/binlogv2/minio_client.py:294

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

What to do

  1. Resolve the 3 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with mgit.py (2), minio_client.py. — One of this dimension's main actionable groups (3 warning-level).
  2. Resolve the 2 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with minio_client.py, mgit.py. — One of this dimension's main actionable groups (2 warning-level).
  3. Resolve the 1 Near-duplicate member pair (107 shared lines) finding(s) in Code Duplication — start with minio_client.py. — One of this dimension's main actionable groups (1 warning-level).

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

D5 · Coupling10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

8 production modules (Cargo+Go+Python+CMake), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence, with abstractness counted on 2 of the 8 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

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

What it measures: Whether a class's methods are focused on a single responsibility.

Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.

Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.

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

1 of 57 classes have LCOM4 above 3.

Low cohesion: _CppLintState (LCOM4 4)internal/core/build-support/cpplint.py:1245

What to do

  1. Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with cpplint.py. — One of this dimension's main actionable groups (1 warning-level).

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

D7 · Architectural Integrity10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the code respects its intended layering / architecture rules.

Method: Enforcement rung (Prevented/Verified/Documented) per checkable ADR via Roslyn, plus dependency cycles via the engine shared with D5/AX3. Deterministic, exact.

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

All 112 mechanizable ADR(s) are enforced: 90 by analyzers, 22 by tests. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).

Checkable ADR rule enforced only by prose: MEP: PyUDF FunctionChain Worker Pool · ×6docs/design-docs/design_docs/20260722-pyudf-function-chain.md

✓ On the Gold path — maintain.

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

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

22591 test methods: 22105 unit, 418 integration, 0 BDD, 68 e2e. The Rust suite contributes 184 `#[test]` function(s) across 41 file(s) declaring at least one; its unit/integration split is Cargo's own — 1 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. The Python suite contributes 5179 test function(s) across 237 file(s) declaring at least one — every `def test…` in a file pytest or unittest would collect, which is those frameworks' own definition of a case; a parametrize table counts once, so this is a floor. Its tier split is read from file names and paths only. The Go suite contributes 17228 test case(s) across 1960 `_test.go` file(s) declaring at least one — every `func Test…(t *testing.T)` that `go test` would collect, plus the suite methods a testify-style runner reaches; a table-driven case list counts once, so this is a floor. Its tier split is INFERRED from file names, paths and build constraints, not declared: 48 of those file(s) use Go's external test package (`package x_test`), which is a visibility boundary rather than a pyramid tier and was not read as one.

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

D12 · Dependency Hygiene7.0 6.9 / 10Adequate✓ 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 6.9 / 10 · rule-coverage 98% · ceiling Verified

114 outdated, 1 author-deprecated direct Go module(s), 2 pinning or checksum defect(s). 147 of 147 direct requirement(s) were graded against proxy.golang.org (0 not served there, 3 publishing no tagged release to be behind). Whether any of these modules is UNMAINTAINED is not graded — proxy.golang.org publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, not a registry one. Known CVEs in this module graph are D30's question, read from REDACTED and go.sum there.

Dependency pinned to a stale untagged commit: github.com/benesch/cgosymbolizer · ×2
Deprecated module: go.opentelemetry.io/otel/exporters/jaeger
Outdated: cloud.google.com/go/storage · ×114

What to do

  1. Resolve the 2 Dependency pinned to a stale untagged commit finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (2 warning-level).
  2. Resolve the 1 Deprecated module finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
  3. Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

D13 · REDACTED Scanning0.0 / 10Critical✓ Tool-verified

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 0.0 / 10 · rule-coverage 100% · ceiling Prevented

6 secret(s) detected.

REDACTED

What to do

  1. Resolve the 6 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (6 issue-level).
  2. Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

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 491 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 21 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. ★ COVERAGE OF THIS VERDICT: it grades this repository's crate dependencies and nothing else. The repository also declares a Go module (REDACTED/go.sum), and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D16 · Bus Factor9.4 / 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.4 / 10 · rule-coverage 100% · ceiling Documented

89 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is tools/mgit.py. Counted over 1584 of the 2250 production source files in this repository: 665 are under the ~2,400-byte size floor this dimension measures over, and the remaining 1 have no attributable history left to measure.

Off-boarding risk: anonymized user #1 · ×6
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.

D17 · Explicit Debt9.8 / 10Stronggated by 528 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

528 deducted task-comment markers across 565420 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 · ×525client/entity/vectors_test.go:71
FixmeComment · ×2internal/proxy/proxy_test.go:3651
XxxCommentinternal/proxy/dql/feature_usage_bench_test.go:38

What to do

  1. Resolve the 525 TodoComment finding(s) in Explicit Debt — start with mock_test.go (36), cpplint.py (21), services.go (12). — One of this dimension's main actionable groups (525 warning-level).
  2. Resolve the 2 FixmeComment finding(s) in Explicit Debt — start with proxy_test.go, pulsar_client.go. — One of this dimension's main actionable groups (2 warning-level).
  3. Resolve the 1 XxxComment finding(s) in Explicit Debt — start with feature_usage_bench_test.go. — One of this dimension's main actionable groups (1 warning-level).

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

D19 · Documentation QualityStrong◐ 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 Strong / 10 · rule-coverage 100% · ceiling Documented

The repository's root README (README.md) and the docs/README.md directory are both excellent: the former gives a clear overview of what Milvus is, its licensing, Docker pull-count badge, roadmap, Slack invite, and Trendshift banner; the latter documents the repo-wide directory map with status columns for each component and links to the milvus-docs repository. The client/README.md (Go MilvusClient) gives a concrete getting started guide with prerequisites, install commands, and API documentation, while the githooks/, scripts/, and tests/READMEs are focused on their own directories and show commands rather than missing installation or usage content. All visible documents are well-structured and complete per their scope. The repository is well documented with a strong README presence for each directory (e.g. deployments/upgrade/, docs/archive/, docs/design-docs/, docs/dev/) and an extensive architecture section for the mlog package. The READMEs are focused on their own directories rather than the repository as a whole, so the root-level overview/installation/usage/contributing sections fall to the top-level root README. There is no single missing document of the type I would call 'outdated', but one internal-focused defect exists in the tests/java_client README: it names an integration test framework and its test cases without explaining what each test does or what context a reader needs to decode, which is jargon ticket-ids style.

What to do

  1. Improve Documentation Quality — currently 8.4/10. — The repository's root README (README.md) and the docs/README.md directory are both excellent: the former gives a clear overview of what Milvus is, its licensing, Docker pull-count badge, roadmap, Slack invite, and Trendshift banner; the latter documents the repo-wide directory map with status columns for each component and links to the milvus-docs repository. The client/README.md (Go MilvusClient) gives a concrete getting started guide with prerequisites, install commands, and API documentation, while the githooks/, scripts/, and tests/READMEs are focused on their own directories and show commands rather than missing installation or usage content. All visible documents are well-structured and complete per their scope. The repository is well documented with a strong README presence for each directory (e.g. deployments/upgrade/, docs/archive/, docs/design-docs/, docs/dev/) and an extensive architecture section for the mlog package. The READMEs are focused on their own directories rather than the repository as a whole, so the root-level overview/installation/usage/contributing sections fall to the top-level root README. There is no single missing document of the type I would call 'outdated', but one internal-focused defect exists in the tests/java_client README: it names an integration test framework and its test cases without explaining what each test does or what context a reader needs to decode, which is jargon ticket-ids style.

Detailed fixes: d19_recommendation.md.

D20 · ADR QualityStrong◐ Sampled · advisory

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

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

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

Evaluated 155 ADR(s) individually; mean quality 8.5/10 (consistently complete and clear). 5 flagged with a specific gap.

Decision and consequences are present but trade-offs (e.g., etcd lease/lease timeout handling, index deletion consistency with MetaTable) are not stated in the visible portiondocs/design-docs/design_docs/20210731-index_design.md
Context/problem (the CreateCollection flow's motivation and why it matters) is absent in favor of only the execution path with proto codedocs/design-docs/design_docs/20211217-milvus_create_collection.md
Decision and consequences are present but the context/problem is thin (only one sentence about ANNS efficiency vs accurate retrieval) and there are no trade-offs for using an approximate enginedocs/design-docs/design_docs/20211223-knowhere_design.md
Context/problem and consequences/trade-offs are absent from the visible textdocs/design-docs/design_docs/cdc/user_docs/02-cdc-replication-quick-start.md
No explicit decision and no consequences/trade-offs for the proposed TransformLog design (e.g. how ObserveMessage is handled, replay semantics)docs/design-docs/design_docs/wal/transformlog/transform_log.md

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

What to do

  1. Resolve the 1 Decision and consequences are present but trade-offs (e.g., etcd… finding(s) in ADR Quality — start with 20210731-index_design.md. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 Context/problem (the CreateCollection flow's motivation and why it… finding(s) in ADR Quality — start with 20211217-milvus_create_collection.md. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 Decision and consequences are present but the context/problem is thin… finding(s) in ADR Quality — start with 20211223-knowhere_design.md. — One of this dimension's main actionable groups (1 warning-level).

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

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.

D22 · Internal API ConsistencyWeak◐ 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 Weak / 10 · rule-coverage 100% · ceiling Verified

3 API inconsistencies across 14 exposed types.

Inconsistent deserialization patterns. Some types use `from_json` with a single `Value` argument, while others use `from_json` with a `Map` and additional context arguments (like `helper`). `ResourceInfo` has two distinct methods `from_json` and `from_global_json` with different signatures, implying different parsing contexts that are not clearly distinguished by naming convention.
Inconsistent naming for default instance retrieval. `LangIdentTokenizer` uses `default()` while `TantivyIndexVersion` uses `default_version()`. This creates ambiguity about whether `default()` is a static factory or an instance method (though signature suggests static), and breaks naming consistency across the API.
Inconsistent constructor signatures. Some tokenizers use `new()` with no arguments, while others require specific parameters. While this reflects different configuration needs, the lack of a unified builder or factory pattern makes the API feel fragmented. Specifically, `NgramTokenizerWithChars` returns a `Result` while others return the type directly, implying potential failure in construction that is not present in others.

What to do

  1. Resolve the 1 Inconsistent deserialization patterns. Some types use `from_json` with a… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 Inconsistent naming for default instance retrieval. `LangIdentTokenizer`… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 Inconsistent constructor signatures. Some tokenizers use `new()` with no… 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.

D25 · ADR ConformanceAdequategated by 1 critical finding◐ Sampled · advisory

What it measures: Whether the code actually follows the decisions recorded in the project's ADRs.

Method: Judged by language model at low temperature against ADRs plus a deterministic structural code summary; findings linked to repo-rooted ADR paths for traceability. Advisory.

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

17 conform / 1 violate across 155 ADRs.

ADR not followed: DataCoord Segment-Scoped Manifest Commit Frameworkdocs/design-docs/design_docs/20260817-datacoord-segment-manifest-commit.md

What to do

  1. Resolve the 1 ADR not followed finding(s) in ADR Conformance — start with 20260817-datacoord-segment-manifest-commit.md. — One of this dimension's main actionable groups (1 issue-level).
  2. Enforce ADR Conformance in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

D28 · Secrets (history)0.0 / 10Critical✓ Tool-verified

What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.

Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.

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

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

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 12 High secret finding(s) in Secrets (history) — start with REDACTED (9), REDACTED (3). — One of this dimension's main actionable groups (12 issue-level).
  2. Resolve the 2 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
  3. Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).

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

D29 · Static Analysis (SAST)0.0 / 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.0 / 10 · rule-coverage 100% · ceiling Documented

743 finding(s): 0 critical, 150 high, 69 medium, 524 low. 85 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 63 file(s) — `client/column/array.go` (lines 26–27, line 27, line 28, …), `client/column/columns.go` (line 420), `client/column/geometry.go` (line 9), `client/column/json.go` (lines 30–31, lines 32–33, line 35), `client/column/scalar.go` (line 32, line 56, line 85, …), … (+58 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 10 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

  1. Resolve the 19 REDACTED finding(s) charged to Static Analysis (SAST) — the other 85 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (104 issue-level, 19 of them charged here).
  2. Resolve the 23 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (23 issue-level).
  3. Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (6 issue-level).

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

D30 · Dependency Vulnerabilities2.9 / 10Weak✓ 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 (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.

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

31 finding(s): 0 critical, 3 high, 28 medium, 0 low.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

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

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

D31 · IaC & Container Security0.0 / 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 0.0 / 10 · rule-coverage 100% · ceiling Documented

253 finding(s): 0 critical, 76 high, 128 medium, 49 low.

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 128 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (42), REDACTED (11), REDACTED (8). — One of this dimension's main actionable groups (128 warning-level).
  2. Resolve the 76 High IaC finding(s) in IaC & Container Security — start with REDACTED (32), REDACTED (11), REDACTED (6). — One of this dimension's main actionable groups (76 issue-level).
  3. Resolve the 49 Low IaC finding(s) in IaC & Container Security — start with REDACTED (19), REDACTED (5), REDACTED (5). — One of this dimension's main actionable groups (49 recommendation-level).

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

D34 · Knowledge Freshness9.6 / 10Adequategated by 2 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.6 / 10 · rule-coverage 100% · ceiling Documented

66 of 1585 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is internal/core/build-support/cpplint.py. Counted over 1585 of the 2250 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned knowledge · ×2internal/core/build-support/cpplint.py:1
Orphaned file · ×64pkg/mq/msgstream/msg_for_user_role.go:1
Further orphaned files (smaller)

What to do

  1. Resolve the 2 Orphaned knowledge finding(s) in Knowledge Freshness — start with cpplint.py, mck.go. — One of this dimension's main actionable groups (2 issue-level).
  2. Resolve the 64 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED (2), msg_for_user_role.go, etcd210.go. — One of this dimension's main actionable groups (64 recommendation-level).
  3. 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.

D35 · Change Coupling10.0 / 10Adequategated by 1 critical finding✓ Tool-verified

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

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

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

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

Strongest change-coupling: REDACTED↔component_param.go 78%

Boundary-crossing change coupling: REDACTED ↔ component_param.goREDACTED:1

What to do

  1. Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).

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

D36 · Supply-chain Provenance & Signing0.0 / 10Critical✓ 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 0.0 / 10 · rule-coverage 100% · ceiling Documented

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

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

  1. Resolve the 11 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (11 warning-level).
  2. Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
  3. Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).

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

D40 · Network Egress Confinement6.0 / 10Adequate✓ Tool-verified

What it measures: Whether Kubernetes workloads restrict network EGRESS with a NetworkPolicy (or Cilium policy), limiting where a compromised pod can send data or reach a command-and-control server. Presence of committed egress-restricting policy, not runtime enforcement.

Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn — language-agnostic): Kubernetes workloads gate applicability; credits a NetworkPolicy / Cilium policy that restricts egress (policyTypes: [Egress] / egress rules). Reward-leaning (neutral floor climbing to 10, never a deduction — baseline misconfigs stay with D31). Deterministic.

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

0/2 network-egress controls present (network policy, egress restriction).

No network policy

What to do

  1. Resolve the 1 No network policy finding(s) in Network Egress Confinement. — One of this dimension's main actionable groups (1 recommendation-level).

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

D41 · Kernel & Syscall Confinement6.0 / 10Adequate✓ Tool-verified

What it measures: Whether Kubernetes workloads confine the kernel boundary — a seccomp profile (RuntimeDefault/Localhost) plus an AppArmor/SELinux mandatory-access-control layer — shrinking the syscall attack surface a container escape would use. Presence of committed confinement config, not runtime enforcement.

Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn): on Kubernetes workloads, credits a seccomp profile (RuntimeDefault/Localhost) and an AppArmor/SELinux MAC layer. Reward-leaning (neutral floor climbing to 10); NotApplicable without workloads. Deterministic.

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

0/13 workload(s) run every container under a seccomp profile; 0/13 declare an AppArmor/SELinux profile.

No seccomp profile · ×13REDACTED:2

What to do

  1. Resolve the 13 No seccomp profile finding(s) in Kernel & Syscall Confinement — start with REDACTED (2), REDACTED, scale-test.yaml. — One of this dimension's main actionable groups (13 recommendation-level).

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

D42 · Runtime Threat Enforcement6.0 / 10Adequate✓ Tool-verified

What it measures: Whether the Kubernetes deployment wires runtime threat enforcement — a detection engine (Tetragon/Falco) and/or an admission-control policy gate (Kyverno / OPA Gatekeeper / PodSecurity). Presence of committed policy, not a runtime guarantee.

Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn): on Kubernetes workloads, credits a runtime threat-detection engine (Tetragon TracingPolicy / Falco) and an admission-control policy (Kyverno / OPA Gatekeeper / PodSecurity). Reward-leaning; NotApplicable without workloads. Deterministic.

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

0/2 runtime-enforcement controls present (threat detection, admission control).

No runtime threat detection
No admission-control policy

What to do

  1. Resolve the 1 No runtime threat detection finding(s) in Runtime Threat Enforcement. — One of this dimension's main actionable groups (1 recommendation-level).
  2. Resolve the 1 No admission-control policy finding(s) in Runtime Threat Enforcement. — One of this dimension's main actionable groups (1 recommendation-level).

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

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.

D44 · Platform End-of-Life10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.

Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.

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

0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 4 platform declaration(s) and 11 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

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

AC2 · Forms & labels4.2 / 10Adequate✓ Tool-verified

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

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

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

  • This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. (×5) — internal/http/webui/telemetry.html:1212, internal/http/webui/telemetry.html:1286, internal/http/webui/telemetry.html:1291, …
  • This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. (×5) — internal/http/webui/telemetry.html:1255, internal/http/webui/telemetry.html:1330, internal/http/webui/telemetry.html:1358, …
  • This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×4) — internal/http/webui/telemetry.html:1256, internal/http/webui/telemetry.html:1331, internal/http/webui/telemetry.html:1387, …

What to do

  • Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure10.0 / 10Exemplary○ Nothing flagged

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.

AC4 · Keyboard semantics5.0 / 10Adequate✓ Tool-verified

Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".

  • A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. — internal/http/webui/telemetry.html:1296

What to do

  • Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC6 · Visual & motion safety4.6 / 10Adequate✓ Tool-verified

Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.

Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.

Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • `.toast` moves (`animation: slideIn 0.3s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — internal/http/webui/telemetry.html:590
  • `.expand-icon` moves (`transition: transform 0.2s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — internal/http/webui/telemetry.html:647
  • `.collapsible-icon` moves (`transition: transform 0.2s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — internal/http/webui/telemetry.html:1016
  • `button._zButton_ok9yu_12._warning_ok9yu_141` sets color: #fff on background-color: #ffb800 — 1.7:1, below the 4.5:1 WCAG AA minimum for normal text. This is a MINIFIED, build-generated sheet — editing the literal here is undone by the next vendor drop or rebuild, so override the rule in your own stylesheet (or fix it upstream / in the source the bundle is built from). — internal/http/webui/assets/index-Cxslai7T.css:1
  • `&:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — internal/http/webui/assets/index-nmS7rbPW.js:197
  • `._loading_ezgk7_12` moves (`animation: _rotate_ezgk7_1 1s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — internal/http/webui/assets/index-Cxslai7T.css:1
  • `._json-detail-wrapper_12ixl_40 ._json-detail-loading-icon_12ixl_50` moves (`animation: _loading_12ixl_1 1s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — internal/http/webui/assets/index-Cxslai7T.css:1
  • `._tools-menu_1f0gw_13` moves (`transition: opacity 315ms cubic-bezier(.4,0,.2,1),transform .21s cubic-bezier(.4,0,.2,1)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — internal/http/webui/assets/index-Cxslai7T.css:1

What to do

  • Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AC7 · A11y enforcement4.0 / 10Adequate✓ Tool-verified

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

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

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

  • No accessibility enforcement found — no automated accessibility check runs over the HTML your app renders. Assert the accessibility invariants over that HTML in the test suite you already have (parse the output and assert, or drive a browser), and gate that test in CI so a regression blocks the merge. What was searched, so you can tell an absence from a miss: the 2 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 test suite you already have: assert the accessibility invariants over the HTML your app renders — parse the rendered output in an existing test, or drive a real browser from one — and gate that test in CI so a regression blocks the merge.
AX10 · Code composition9.9 / 10Exemplary✓ Tool-verified

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

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

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

What to do

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

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

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

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

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

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

AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.

Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.

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.

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

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

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

What to do

  • Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
  • Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
  • Add a README to the 2 of 3 project(s) that lack one — worth up to 1.3 pts.
M2 · Architecture documentation10.0 / 10Exemplary✓ 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.

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

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

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

M4 · Documentation accuracy7.6 / 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.

  • README advertises a microservices architecture, but the repo is a single project with no service manifests — searched for: `microservice`, `service-mesh`, `istio`. Each was matched case- and separator-insensitively against file and directory NAMES anywhere in the tree, and against the CONTENTS of manifest and configuration files (package.json and other *.json, *.csproj, *.props, *.sln/*.slnx, *.yml, *.toml, *.config, tool configs such as eslint.config.js, REDACTED); the README's own prose never counts, so a claim is never refuted by merely being made. Nothing outside that search was read — a footprint living only in a submodule, in a file type not listed here, or under a name none of those terms matches is not seen, and this row is then wrong. — README.md:85
  • docs/dev/README.md names `docs/developer_guides/`, but no file or folder `docs/developer_guides` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/dev/README.md:10
  • docs/dev/error_handling_casebook.md names `internal/proxy/search_reduce_util.go`, but no file or folder `internal/proxy/search_reduce_util.go` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/dev/error_handling_casebook.md:95
  • tests/integration/README.md changes into `[milvus-folder]/deployments/docker/dev`, but no such folder exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — tests/integration/README.md:43
  • deployments/monitor/grafana/README.md links to `monitor_overview.md`, but `deployments/monitor/grafana/monitor_overview.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — deployments/monitor/grafana/README.md:5
  • docs/agent_guides/observability/logging.md names `github.com/milvus-io/milvus/pkg/v3/mlog`, but no file or folder `github.com/milvus-io/milvus/pkg/v3/mlog` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/agent_guides/observability/logging.md:3
  • docs/design-docs/design_docs/20211214-milvus_hybrid_ts.md links to `./milvus_timesync_en.md`, but `docs/design-docs/design_docs/milvus_timesync_en.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/design-docs/design_docs/20211214-milvus_hybrid_ts.md:3
  • docs/design-docs/design_docs/20260105-external_table.md names `milvus.proto`, but no file or folder `milvus.proto` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/design-docs/design_docs/20260105-external_table.md:164
  • docs/design-docs/design_docs/20260105-external_table.md names `internal/proxy/task.go`, but no file or folder `internal/proxy/task.go` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/design-docs/design_docs/20260105-external_table.md:409
  • docs/design-docs/design_docs/20260105-external_table.md names `schema.proto`, but no file or folder `schema.proto` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/design-docs/design_docs/20260105-external_table.md:426
  • docs/design-docs/design_docs/20260105-external_table.md names `internal/proxy/task_insert.go`, but no file or folder `internal/proxy/task_insert.go` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/design-docs/design_docs/20260105-external_table.md:590
  • docs/design-docs/design_docs/20260105-external_table.md names `internal/proxy/task_delete.go`, but no file or folder `internal/proxy/task_delete.go` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/design-docs/design_docs/20260105-external_table.md:591
  • docs/design-docs/design_docs/20260105-external_table.md names `internal/proxy/task_upsert.go`, but no file or folder `internal/proxy/task_upsert.go` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/design-docs/design_docs/20260105-external_table.md:592
  • docs/design-docs/design_docs/20260105-external_table.md names `internal/proxy/task_import.go`, but no file or folder `internal/proxy/task_import.go` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/design-docs/design_docs/20260105-external_table.md:593
  • docs/design-docs/design_docs/20260105-external_table.md names `internal/proxy/task_flush.go`, but no file or folder `internal/proxy/task_flush.go` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/design-docs/design_docs/20260105-external_table.md:594
  • docs/design-docs/design_docs/20260129-add-function-field-design.md names `internal/proxy/task.go`, but no file or folder `internal/proxy/task.go` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/design-docs/design_docs/20260129-add-function-field-design.md:198
  • docs/design-docs/design_docs/20260129-add-function-field-design.md names `internal/datacoord/compaction_policy_backfill.go`, but no file or folder `internal/datacoord/compaction_policy_backfill.go` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/design-docs/design_docs/20260129-add-function-field-design.md:391
  • docs/design-docs/design_docs/20260129-add-function-field-design.md names `internal/datanode/compactor/backfill_compactor.go`, but no file or folder `internal/datanode/compactor/backfill_compactor.go` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/design-docs/design_docs/20260129-add-function-field-design.md:466
  • docs/design-docs/design_docs/20260129-add-function-field-design.md names `internal/querynodev2/pipeline/embedding_node.go`, but no file or folder `internal/querynodev2/pipeline/embedding_node.go` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/design-docs/design_docs/20260129-add-function-field-design.md:524
  • docs/design-docs/design_docs/20260129-add-function-field-design.md names `internal/util/schema_util.go`, but no file or folder `internal/util/schema_util.go` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/design-docs/design_docs/20260129-add-function-field-design.md:658
  • docs/design-docs/design_docs/20260129-add-function-field-design.md names `internal/util/schema_util_test.go`, but no file or folder `internal/util/schema_util_test.go` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/design-docs/design_docs/20260129-add-function-field-design.md:997
  • docs/design-docs/design_docs/20260129-add-function-field-design.md names `internal/datacoord/compaction_policy_backfill_test.go`, but no file or folder `internal/datacoord/compaction_policy_backfill_test.go` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/design-docs/design_docs/20260129-add-function-field-design.md:998
  • docs/design-docs/design_docs/20260129-add-function-field-design.md names `internal/datacoord/compaction_task_backfill_test.go`, but no file or folder `internal/datacoord/compaction_task_backfill_test.go` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/design-docs/design_docs/20260129-add-function-field-design.md:999
  • docs/design-docs/design_docs/20260129-add-function-field-design.md names `internal/datanode/compactor/backfill_compactor_test.go`, but no file or folder `internal/datanode/compactor/backfill_compactor_test.go` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/design-docs/design_docs/20260129-add-function-field-design.md:1000
  • docs/design-docs/design_docs/20260129-add-function-field-design.md links to `../architecture.md`, but `docs/design-docs/architecture.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/design-docs/design_docs/20260129-add-function-field-design.md:1037
  • docs/design-docs/design_docs/20260129-add-function-field-design.md links to `../segcore-pipeline.md`, but `docs/design-docs/segcore-pipeline.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/design-docs/design_docs/20260129-add-function-field-design.md:1038
  • docs/design-docs/design_docs/20260129-add-function-field-design.md links to `../reduce-mechanism.md`, but `docs/design-docs/reduce-mechanism.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/design-docs/design_docs/20260129-add-function-field-design.md:1039
  • docs/design-docs/design_docs/20260129-add-function-field-design.md links to `../../pkg/util/bm25/bm25.go`, but `docs/pkg/util/bm25/bm25.go` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/design-docs/design_docs/20260129-add-function-field-design.md:1040
  • docs/design-docs/design_docs/20260129-search-orderby.md names `internal/proxy/search_pipeline.go`, but no file or folder `internal/proxy/search_pipeline.go` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/design-docs/design_docs/20260129-search-orderby.md:220
  • docs/design-docs/design_docs/20260129-search-orderby.md names `internal/proxy/search_pipeline_test.go`, but no file or folder `internal/proxy/search_pipeline_test.go` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/design-docs/design_docs/20260129-search-orderby.md:316
  • docs/design-docs/design_docs/20260129-search-orderby.md names `internal/proxy/search_util.go`, but no file or folder `internal/proxy/search_util.go` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/design-docs/design_docs/20260129-search-orderby.md:340
  • docs/design-docs/design_docs/20260129-search-orderby.md names `internal/proxy/task_search.go`, but no file or folder `internal/proxy/task_search.go` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/design-docs/design_docs/20260129-search-orderby.md:342
  • docs/design-docs/design_docs/20260129-search-orderby.md names `internal/proxy/task.go`, but no file or folder `internal/proxy/task.go` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/design-docs/design_docs/20260129-search-orderby.md:343
  • docs/design-docs/design_docs/20260130-embeded-group-by.md names `internal/proxy/embedded_group_operator.go`, but no file or folder `internal/proxy/embedded_group_operator.go` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/design-docs/design_docs/20260130-embeded-group-by.md:289
  • docs/design-docs/design_docs/20260130-embeded-group-by.md names `internal/core/src/segcore/reduce/GroupReduce.cpp`, but no file or folder `internal/core/src/segcore/reduce/GroupReduce.cpp` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/design-docs/design_docs/20260130-embeded-group-by.md:298
  • docs/design-docs/design_docs/20260130-embeded-group-by.md names `internal/proxy/search_util.go`, but no file or folder `internal/proxy/search_util.go` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/design-docs/design_docs/20260130-embeded-group-by.md:299
  • docs/design-docs/design_docs/20260130-embeded-group-by.md names `internal/proxy/task_search.go`, but no file or folder `internal/proxy/task_search.go` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/design-docs/design_docs/20260130-embeded-group-by.md:300
  • docs/design-docs/design_docs/20260203-query-orderby.md names `internal/proxy/task_query.go`, but no file or folder `internal/proxy/task_query.go` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/design-docs/design_docs/20260203-query-orderby.md:78
  • docs/design-docs/design_docs/20260203-query-orderby.md names `internal/proxy/query_pipeline.go`, but no file or folder `internal/proxy/query_pipeline.go` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/design-docs/design_docs/20260203-query-orderby.md:214
  • docs/design-docs/design_docs/20260209-scalar-index-unified-format.md documents the environment variable `SORT_INDEX_META`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/design-docs/design_docs/20260209-scalar-index-unified-format.md:414

What to do

  • Reconcile the README with reality: README advertises a microservices architecture, but the repo is a single project with no service manifests; docs/dev/README.md names `docs/developer_guides/`, but no file or folder `docs/developer_guides` exists; docs/dev/error_handling_casebook.md names `internal/proxy/search_reduce_util.go`, but no file or folder `internal/proxy/search_reduce_util.go` exists; tests/integration/README.md changes into `[milvus-folder]/deployments/docker/dev`, but no such folder exists; deployments/monitor/grafana/README.md links to `monitor_overview.md`, but `deployments/monitor/grafana/monitor_overview.md` does not exist.
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.

P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.

Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.

P2 · Observability9.1 / 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 5/7 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `cmd/tools/binlogv2`, `deployments/offline`.

What to do

  • Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
P3 · Security & performance tooling6.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

  • Enable Dependabot/Renovate or a dependency-review gate.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
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.

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

  • No persistence guard on critical data stores — use Docker named volumes (or your orchestrator's persistent-volume equivalent) so the data store can't be wiped by a container recreate (or, in cloud, set purge-protection / soft-delete / prevent_destroy).
P6 · Release Hygiene5.0 / 10Adequate✓ Tool-verified

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

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

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

What to do

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

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

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

  • `http.Client{` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — REDACTED:427

What to do

  • Give every `http.Client` an explicit `Timeout` (never call `http.Get`/`http.Post` or `http.DefaultClient`, which have none), or build each request with `http.NewRequestWithContext` under a `context.WithTimeout`; add retry with back-off (`hashicorp/go-retryablehttp`) and a breaker (`sony/gobreaker`) around dependencies that fail.
PF1 · Benchmark discipline9.5 / 10Exemplary✓ Tool-verified

Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.

Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.

PF2 · Allocation hygiene7.7 / 10Strong✓ Tool-verified

Readiness · Performance — Whether the code is written to minimise allocations so it doesn't pressure its host's memory manager — buffer/slice views over copies, object pooling, stack or value-type allocation, and buffer writers. Reward-only: credited where present, never penalised where a simpler style is fine.

Method: Production-source scan: density (per 1k LoC) of allocation-aware APIs — in .NET Span/Memory, ArrayPool/ObjectPool, stackalloc, ValueTask, value-type structs, IBufferWriter, string.Create, SkipLocalsInit; off .NET, with comments and strings blanked, Go's sync.Pool, preallocated slices/maps, Grow, strconv.Append* and buf[:0] reuse; the JVM's NIO buffer views, MemorySegment, primitive collections, pools and literal presizes (plus Kotlin primitive arrays and value classes, Scala AnyVal and @specialized); Swift's reserveCapacity, ContiguousArray, withUnsafe* access and ~Copyable. Activated off .NET on the same floor (400 lines, and benchmarks or 8 uses); Rust and garbage-collected scripting languages are not applicable. Reward-only. Deterministic, syntax/text detection.

What to do

  • Raise allocation-aware density on the hot paths — currently 2108 use(s) across 609,544 production line(s) (~3.5/1k). More of the idioms below on the allocation-heavy paths climbs this toward 10.
  • Go: on hot paths, reuse buffers and objects through sync.Pool, preallocate slices and maps with make([]T, 0, n) / make(map[K]V, n), size builders with Grow, append with strconv.Append*, and reslice with buf[:0] instead of allocating anew.
PF3 · Async & latency hygiene10.0 / 10Exemplary✓ Tool-verified

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

Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.

X1 · Async correctness10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.

Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.

X12 · Unreachable branch8.0 / 10Strong✓ Tool-verified

Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.

Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.

  • `"bfloat16" in field_name.lower()` can only be reached when `"float16" in field_name.lower()` on line 63 was false — but every string satisfying the first satisfies the second, so this `elif` never runs. Test the more specific literal `"bfloat16"` BEFORE the more general `"float16"`, or make the arms mutually exclusive. — cmd/tools/binlogv2/parquet_analyzer/vector_deserializer.py:65

What to do

  • Each finding names the span that makes the branch dead and the span it is dead because of. Confirm from the two, then delete the dead arm or fix the predicate that was meant to be reachable.
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

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

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

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

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

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

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

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

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

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

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

X2 · Cancellation propagation9.3 / 10Exemplary✓ Tool-verified

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

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

  • Only 8/9 functions that make a cancellable request (net/http, net.Dial) accept a context.Context or pass one on, so a request keeps running after whatever wanted it has given up — a cancelled request, a shutdown, an expired deadline. Take `ctx context.Context` as the first parameter and build the request with it (`http.NewRequestWithContext`, `DialContext`); where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
  • `GetConn` calls `grpc.DialContext(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`. — internal/util/function/models/zilliz/zilliz_client.go:91

What to do

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

Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.

Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.

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

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

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

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

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

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

X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged

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

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

X25 · Inert configuration knob10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.

Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.

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

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

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

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

Other · Code Health — Whether a `for` loop leaves the `dict`, `set` or `deque` it is walking alone — CPython's iterators over those check that the collection has not changed size since the loop began, so a body that removes from (or empties) the very collection the loop is walking makes the next step raise `RuntimeError: dictionary changed size during iteration` and the remaining items are never seen.

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

X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.

Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.

X3 · Exception handling7.6 / 10Strong✓ Tool-verified

Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.

Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.

  • An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×7) — client/milvusclient/telemetry.go:1224, cmd/tools/binlogv2/minio_parquet_analyzer.py:365, cmd/tools/binlogv2/minio_client.py:290, …
  • `if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×22) — client/milvusclient/telemetry.go:1810, REDACTED:59, cmd/components/query_node.go:74, …
  • `if _, err := rand.Read(buf[:]); err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — client/milvusclient/interceptors.go:123
  • `if err := st.tryDropTaskOnWorker(cluster); err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×2) — internal/datacoord/task_stats.go:142, internal/datacoord/task_stats.go:312
  • `if err := it.tryDropTaskOnWorker(cluster); err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — internal/datacoord/task_index.go:277
  • `if err := at.tryDropTaskOnWorker(cluster); err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — internal/datacoord/task_analyze.go:123
  • `if err := json.Unmarshal([]byte(externalSpec), &spec); err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — internal/datacoord/snapshot_export_manager.go:958
  • `if err := jc.transitionTo(internalpb.ImportJobState_Completed, UpdateJobCompleteTime(completeTime)); err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — REDACTED:92
  • `if err := jc.transitionTo(internalpb.ImportJobState_IndexBuilding); err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — REDACTED:167
  • `if err := jc.transitionTo(internalpb.ImportJobState_Uncommitted); err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — REDACTED:197
  • `if err := metricsinfo.UnmarshalComponentInfos(resp.GetResponse(), &infos); err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — internal/datacoord/compaction_policy_forcemerge.go:250
  • `if _, err := strconv.ParseInt(parts[i+offset], 10, 64); err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — internal/datanode/importv2/copy_segment_utils.go:1445

What to do

  • Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.

Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.

X4 · Structured logging10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.

Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.

WCAG coverage — what static analysis assessed

Statically assessed 12 of 55 WCAG 2.2 Level A/AA success criteria (22%; ≈24% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 43 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).

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

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

Reference — by lens

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

LensScoreRatingImpact
Code Health91%ExemplarySolid.
Architecture100%ExemplaryStrongest area.
Maturity84%ExemplarySolid.
Readiness55%Adequate — gated by D13, P7Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security41%Weak — gated by D28, D29, D30, D31, D36Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Accessibility49%AdequateAcceptable, with room to improve.
Performance88%ExemplarySolid.
Unscored — 3 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.

  • D11 Test Reliability — 4 observation(s) recorded · This repository declares 4 of its own test(s) unreliable. The built-in reliability runner does not support this repository's ecosystem (.go, .py), so the suite was not re-run and no reliability score is given — these are the repository's own declarations, not our measurement.
  • X10 Duplicated predicate — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 control(s) we could not find positive evidence for

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

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

  • AC1 Text alternatives — No image/media element found in the parsed markup — AC1 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 — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written.
  • 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
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — compose up failed (exit 18 — an image could not be pulled) — pulsar Error Get "https://registry-1.docker.io/v2/": Forbidden gcpnative Error Get "https://registry-1.docker.io/v2/": Forbidden minio Error context canceled etcd Error context canceled gpubuilder Warning context canceled azurite Error context canceled builder Warning context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: gpubuilder Warning context canceled pulsar Error context canceled azurite Error context canceled gcpnative Error context canceled minio Error context canceled jaeger Error context canceled WARNING: Some service image(s) must be built from source by running: docker compose build builder gpubuilder Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
  • C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • 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.
  • D1 Cyclomatic Complexity — cyclomatic complexity not measured — .c, .cpp, .go, .groovy exposed no member bodies
  • D10 Test Quality — ~1146461 lines of test source are present (.go, .py) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
  • D15 Churn × Complexity Hotspots — complexity unreadable for .c, .cpp, .go, .groovy — churn × complexity hotspots could not be measured
  • 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.
  • D2 Cognitive Complexity — cognitive complexity not measured — .c, .cpp, .go, .groovy exposed no member bodies
  • D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D24 Comment Value — No inline comments to assess — comment value is not applicable here.
  • D26 Project Cohesion — D26 measured no build unit over this repository's .c, .cpp, .go, .groovy source. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D27 Navigability — D27 reads resolved call sites in the languages it reads only — this repository's production source is .c, .cpp, .go, .groovy, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D3 God Classes — Most of this repository's production source (.c, .cpp, .go, .groovy) was not read by god-class detection, so class size was not assessed for the languages that are the product — whatever else this pass did read is not this repository's class size. Not scored — this is a gap in the analyzer, not a verdict about this repository.
  • D32 Data Compliance (PII/GDPR) — 29 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
  • D8 Code Coverage — Coverage not included — suite not readable by the collector
  • DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (24 value object(s))
  • 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 — no mutating command handlers or message consumers detected — idempotency check not applicable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
  • IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • P12 CI test-gate honesty — Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
  • P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
  • P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (`go test -coverprofile=coverage.out ./...`) 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
  • 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.
  • X16 Unfloored truncation loop — 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
  • X18 Disposal-pattern 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
  • X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X29 Per-element action decided by a fixed element — 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
  • X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • 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 — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 272 finding(s)
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 79 more in this group — see findings.md.
D31 · IaC & Container Security · High IaC · ×76
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 51 more in this group — see findings.md.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D28 · Secrets (history) · High secret · ×12
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D13 · REDACTED Scanning · Leaked secret · ×6
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC2 · Forms & labels · <input> without a programmatic label · ×5
  • <input> without a programmatic label internal/http/webui/telemetry.html:1212 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label internal/http/webui/telemetry.html:1286 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label internal/http/webui/telemetry.html:1291 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label internal/http/webui/telemetry.html:1359 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label internal/http/webui/telemetry.html:1393 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC2 · Forms & labels · <label> that labels no control · ×5
  • <label> that labels no control internal/http/webui/telemetry.html:1255 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control internal/http/webui/telemetry.html:1330 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control internal/http/webui/telemetry.html:1358 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control internal/http/webui/telemetry.html:1386 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control internal/http/webui/telemetry.html:1392 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
D11 · Test Reliability · Test declared unreliable · ×4
  • Test declared unreliable: TestStructArrayElementFilterSearchBasicCosine tests/go_client/testcases/struct_array_element_search_test.go:48 — This test is disabled or skipped with a reason naming unreliability — the repository's own words: "xfail in python: flaky element-level search on growing segment returns wrong element-to-row mapping". A test that is skipped for flakiness is neither passing nor protecting the code it covers; either stabilise it or delete it, but do not leave it disabled indefinitely. (Found by reading the repository's own test source — the suite itself was not re-run, since the reliability runner does not support this ecosystem.)
  • Test declared unreliable: TestStructArrayElementFilterSearchBasicL2 tests/go_client/testcases/struct_array_element_search_test.go:52 — This test is disabled or skipped with a reason naming unreliability — the repository's own words: "xfail in python: same flaky element-to-row mapping issue". A test that is skipped for flakiness is neither passing nor protecting the code it covers; either stabilise it or delete it, but do not leave it disabled indefinitely. (Found by reading the repository's own test source — the suite itself was not re-run, since the reliability runner does not support this ecosystem.)
  • Test declared unreliable: test_search_pagination_dense_vectors_indices_metrics_growing tests/python_client/milvus_client/test_milvus_client_search_pagination.py:848 — This test is disabled or skipped with a reason naming unreliability — the repository's own words: "unstable: pagination consistency varies across index types, needs investigation". A test that is skipped for flakiness is neither passing nor protecting the code it covers; either stabilise it or delete it, but do not leave it disabled indefinitely. (Found by reading the repository's own test source — the suite itself was not re-run, since the reliability runner does not support this ecosystem.)
  • Test declared unreliable: test_search_with_text_match_filter_normal_zh tests/python_client/milvus_client/test_milvus_client_search_text_match.py:331 — This test is disabled or skipped with a reason naming unreliability — the repository's own words: "unstable: jieba tokenization vs Python substring mismatch, see analysis below". A test that is skipped for flakiness is neither passing nor protecting the code it covers; either stabilise it or delete it, but do not leave it disabled indefinitely. (Found by reading the repository's own test source — the suite itself was not re-run, since the reliability runner does not support this ecosystem.)
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC2 · Forms & labels · <select> without a programmatic label · ×3
  • <select> without a programmatic label internal/http/webui/telemetry.html:1256 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <select> without a programmatic label internal/http/webui/telemetry.html:1331 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <select> without a programmatic label internal/http/webui/telemetry.html:1387 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
D28 · Secrets (history) · REDACTED · ×2
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · High CVE · ×2
  • REDACTED
  • REDACTED
D34 · Knowledge Freshness · Orphaned knowledge · ×2
  • Orphaned knowledge internal/core/build-support/cpplint.py:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
  • Orphaned knowledge cmd/milvus/mck.go:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
AC2 · Forms & labels · <textarea> without a programmatic label · ×1
  • <textarea> without a programmatic label internal/http/webui/telemetry.html:1302 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
AC4 · Keyboard semantics · Click handler on a non-interactive <div> · ×1
  • Click handler on a non-interactive <div> internal/http/webui/telemetry.html:1296 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
D25 · ADR Conformance · ADR not followed · ×1
  • ADR not followed: DataCoord Segment-Scoped Manifest Commit Framework docs/design-docs/design_docs/20260817-datacoord-segment-manifest-commit.md — The summary shows no SegmentInfo/manifest types and no constructor/method parameters for the commit framework, contradicting the presence of a segment-manifest-commit serialization. (docs/design-docs/design_docs/20260817-datacoord-segment-manifest-commit.md)
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D30 · Dependency Vulnerabilities · High vulnerability · ×1
  • REDACTED
D35 · Change Coupling · Boundary-crossing change coupling · ×1
  • Boundary-crossing change coupling: REDACTED ↔ component_param.go REDACTED:1 — `REDACTED` (context internal) and `pkg/util/paramtable/component_param.go` (context pkg) sit in DIFFERENT parts of the tree yet change together 78% of the time (14 of the 18 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 14 shared commits counted here, the most recent 3 are `42d337e7` feat: Support precomputed sparse vectors in external collections (#53…; `a08a3474` enhance: configure storage CPU and IO runtimes together (#54197); `48faae3b` enhance: parallelize json stats build (#52120) — run `git show` on any of them.
Serious — 871 finding(s)
D17 · Explicit Debt · TodoComment · ×525
  • TodoComment client/entity/vectors_test.go:71 — // TODO calculate max precision loss — 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 client/milvusclient/results.go:205 — // TODO maybe support Array and just fill data — 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 client/milvusclient/interceptors.go:47 — // ClientRequestMsecKey temp const value, TODO use common package def after upgrading milvus/pkg version — 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 client/row/schema.go:40 — // TODO add PrimaryKey() interface later — 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 client/row/data.go:138 — // TODO @congqixia, add strict mode if needed — 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 cmd/milvus/main_entry.go:53 — // TODO: after remove all streamingutil.IsStreamingServiceEnabled(), we can remove this code. — 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 cmd/tools/config-docs-generator/main.go:117 — // TODO: — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment REDACTED:221 — // TODO: — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment cmd/tools/migration/backend/etcd210.go:451 — // TODO: optimize this if memory consumption is too large. — 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 cmd/tools/migration/meta/210_to_220.go:215 — // TODO: maybe a constraint is better. — 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 cmd/tools/migration/migration/runner.go:122 — // TODO: more accurate. — 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 cmd/tools/migration/migration/runner.go:236 — // TODO: better to wrap this 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.
  • TodoComment internal/coordinator/snmanager/streaming_node_manager.go:23 — // TODO: can be removed after streaming service fully manage all growing data. — 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 internal/core/build-support/cpplint.py:1836 — # TODO(unknown): if delimiter is not None here, we might want to — 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 internal/core/build-support/cpplint.py:2839 — # TODO(unknown): We always want to check end of namespace comments — 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 internal/core/build-support/cpplint.py:3054 — # TODO(unknown): unexpected #else, issue warning? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment internal/core/build-support/cpplint.py:3069 — # TODO(unknown): unexpected #endif, issue warning? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment internal/core/build-support/cpplint.py:3072 — # TODO(unknown): Update() is too long, but we will refactor later. — 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 internal/core/build-support/cpplint.py:3344 — # TODO(unknown): Could it be expanded safely to arbitrary references, — 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 internal/core/build-support/cpplint.py:3492 — # TODO(unknown): Space after an operator function seem to be a common — 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 internal/core/build-support/cpplint.py:3712 — # TODO(unknown): Don't complain if line before blank line, and line after, — 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 internal/core/build-support/cpplint.py:3835 — # though, so we punt on this one for now. TODO. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment internal/core/build-support/cpplint.py:3978 — # TODO(unknown): clarify if 'if (1) { return 1;}' is requires one more — 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 internal/core/build-support/cpplint.py:4764 — # TODO(unknown): remove this once cpplint has better support for — 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 internal/core/build-support/cpplint.py:5158 — # TODO(unknown): Audit cpplint.py to see what places could be profitably — 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.
  • + 500 more in this group — see findings.md.
D31 · IaC & Container Security · Medium IaC · ×128
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 103 more in this group — see findings.md.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×33
  • Swallowed exception (caught, then discarded) client/milvusclient/telemetry.go:1810 — `if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) client/milvusclient/interceptors.go:123 — `if _, err := rand.Read(buf[:]); err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) REDACTED:59 — `if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) cmd/components/query_node.go:74 — `if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) cmd/components/proxy.go:75 — `if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) cmd/components/mix_coord.go:73 — `if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) cmd/components/data_node.go:74 — `if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) cmd/tools/datameta/main.go:47 — `if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) cmd/tools/migration/migration/runner.go:124 — `if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) internal/datacoord/task_stats.go:142 — `if err := st.tryDropTaskOnWorker(cluster); err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) internal/datacoord/task_stats.go:290 — `if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) internal/datacoord/task_stats.go:312 — `if err := st.tryDropTaskOnWorker(cluster); err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) internal/datacoord/task_index.go:277 — `if err := it.tryDropTaskOnWorker(cluster); err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) internal/datacoord/task_index.go:443 — `if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) internal/datacoord/task_analyze.go:123 — `if err := at.tryDropTaskOnWorker(cluster); err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) internal/datacoord/snapshot_export_manager.go:958 — `if err := json.Unmarshal([]byte(externalSpec), &spec); err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) internal/datacoord/index_meta.go:1548 — `if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) internal/datacoord/index_meta.go:1579 — `if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) REDACTED:92 — `if err := jc.transitionTo(internalpb.ImportJobState_Completed, UpdateJobCompleteTime(completeTime)); err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) REDACTED:167 — `if err := jc.transitionTo(internalpb.ImportJobState_IndexBuilding); err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) REDACTED:197 — `if err := jc.transitionTo(internalpb.ImportJobState_Uncommitted); err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) internal/datacoord/import_util.go:1224 — `if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) internal/datacoord/import_meta.go:467 — `if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) internal/datacoord/garbage_collector.go:1281 — `if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) internal/datacoord/feature_usage.go:75 — `if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • + 8 more in this group — see findings.md.
D29 · Static Analysis (SAST) · REDACTED · ×21
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · Medium advisory (unsound) · ×11
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D36 · Supply-chain Provenance & Signing REDACTED · ×11
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×10
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×8
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×8
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · Medium CVE · ×7
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
X3 · Exception handling · Swallowed exception (empty catch) · ×7
  • Swallowed exception (empty catch) client/milvusclient/telemetry.go:1224 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) cmd/tools/binlogv2/minio_parquet_analyzer.py:365 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) cmd/tools/binlogv2/minio_client.py:290 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) cmd/tools/binlogv2/parquet_analyzer/vector_deserializer.py:40 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) cmd/tools/binlogv2/parquet_analyzer/vector_deserializer.py:287 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) cmd/tools/binlogv2/parquet_analyzer/vector_deserializer.py:349 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) internal/core/conanfile.py:112 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
AC6 · Visual & motion safety · Animation without a prefers-reduced-motion guard · ×6
  • Animation without a prefers-reduced-motion guard internal/http/webui/telemetry.html:590 — `.toast` moves (`animation: slideIn 0.3s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard internal/http/webui/telemetry.html:647 — `.expand-icon` moves (`transition: transform 0.2s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard internal/http/webui/telemetry.html:1016 — `.collapsible-icon` moves (`transition: transform 0.2s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard internal/http/webui/assets/index-Cxslai7T.css:1 — `._loading_ezgk7_12` moves (`animation: _rotate_ezgk7_1 1s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard internal/http/webui/assets/index-Cxslai7T.css:1 — `._json-detail-wrapper_12ixl_40 ._json-detail-loading-icon_12ixl_50` moves (`animation: _loading_12ixl_1 1s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard internal/http/webui/assets/index-Cxslai7T.css:1 — `._tools-menu_1f0gw_13` moves (`transition: opacity 315ms cubic-bezier(.4,0,.2,1),transform .21s cubic-bezier(.4,0,.2,1)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
D30 · Dependency Vulnerabilities · Medium vulnerability · ×5
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · Medium advisory (unmaintained) · ×5
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×3
  • Duplicated block (12 lines × 2) tools/mgit.py:951 — tools/mgit.py:951-962 | tools/mgit.py:1291-1302 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (12 lines × 2) tools/mgit.py:2276 — tools/mgit.py:2276-2287 | tools/mgit.py:2341-2352 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (12 lines × 2) cmd/tools/binlogv2/minio_client.py:60 — cmd/tools/binlogv2/minio_client.py:60-71 | cmd/tools/binlogv2/minio_parquet_analyzer.py:58-69 — before extracting anything, compare `cmd/tools/binlogv2/minio_client.py` and `cmd/tools/binlogv2/minio_parquet_analyzer.py` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 315 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D12 · Dependency Hygiene · Dependency pinned to a stale untagged commit · ×2
  • Dependency pinned to a stale untagged commit: github.com/benesch/cgosymbolizer — Direct dependency `github.com/benesch/cgosymbolizer` is required at `v0.0.0-20190515212042-bec6fe6e597b` in REDACTED — a pseudo-version, which pins an UNTAGGED commit from 2019-05-15, 7.4 years ago. The pin itself is exact, so this is not a reproducibility defect, and it is not a claim that the module is unmaintained. What it says is that this repository tracks no RELEASE of `github.com/benesch/cgosymbolizer` and has not moved this requirement in 7.4 years: every fix the module has published since that commit — including any security fix — is absent from this build, whether the module went quiet or moved on without you. Check whether `github.com/benesch/cgosymbolizer` now publishes tagged releases and move the requirement to one; if it publishes none, re-pin to a current commit.
  • Dependency pinned to a stale untagged commit: github.com/json-iterator/go — Direct dependency `github.com/json-iterator/go` is required at `v1.1.13-0.20220915233716-71ac16282d12` in REDACTED — a pseudo-version, which pins an UNTAGGED commit from 2022-09-15, 4.1 years ago. The pin itself is exact, so this is not a reproducibility defect, and it is not a claim that the module is unmaintained. What it says is that this repository tracks no RELEASE of `github.com/json-iterator/go` and has not moved this requirement in 4.1 years: every fix the module has published since that commit — including any security fix — is absent from this build, whether the module went quiet or moved on without you. Check whether `github.com/json-iterator/go` now publishes tagged releases and move the requirement to one; if it publishes none, re-pin to a current commit.
D17 · Explicit Debt · FixmeComment · ×2
  • FixmeComment internal/proxy/proxy_test.go:3651 — // FIXME(dragondriver) — 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 pkg/mq/msgstream/mqwrapper/pulsar/pulsar_client.go:192 — // FIXME(yukun): pulsar.client is a singleton, so can't invoke this close when server run — 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.
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×2
  • Duplicated block (7 lines × 2) cmd/tools/binlogv2/minio_client.py:596 — cmd/tools/binlogv2/minio_client.py:596-602 | cmd/tools/binlogv2/minio_parquet_analyzer.py:702-708 — before extracting anything, compare `cmd/tools/binlogv2/minio_client.py` and `cmd/tools/binlogv2/minio_parquet_analyzer.py` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 315 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `cmd/tools/binlogv2/minio_parquet_analyzer.py:699` calls `add_argument` and `cmd/tools/binlogv2/minio_client.py:593` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (7 lines × 2) tools/mgit.py:2078 — tools/mgit.py:2078-2084 | tools/mgit.py:2174-2180 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (1.7 · ×1
  • Low contrast colour pair in CSS (1.7:1) internal/http/webui/assets/index-Cxslai7T.css:1 — `button._zButton_ok9yu_12._warning_ok9yu_141` sets color: #fff on background-color: #ffb800 — 1.7:1, below the 4.5:1 WCAG AA minimum for normal text. This is a MINIFIED, build-generated sheet — editing the literal here is undone by the next vendor drop or rebuild, so override the rule in your own stylesheet (or fix it upstream / in the source the bundle is built from).
AC6 · Visual & motion safety · Focus outline removed in CSS without a · ×1
  • Focus outline removed in CSS without a :focus replacement internal/http/webui/assets/index-nmS7rbPW.js:197 — `&:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
AC7 · A11y enforcement · Accessibility enforcement below the top rung · ×1
  • Accessibility enforcement below the top rung — No accessibility enforcement found — no automated accessibility check runs over the HTML your app renders. Assert the accessibility invariants over that HTML in the test suite you already have (parse the output and assert, or drive a browser), and gate that test in CI so a regression blocks the merge. What was searched, so you can tell an absence from a miss: the 2 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.
D12 · Dependency Hygiene · Deprecated module · ×1
  • Deprecated module: go.opentelemetry.io/otel/exporters/jaeger — `go.opentelemetry.io/otel/exporters/jaeger` is required at v1.13.0 in REDACTED, and its author has DEPRECATED the module: "This module is no longer supported. OpenTelemetry dropped support for Jaeger exporter in July 2023. Jaeger officially accepts and recommends using OTLP. Use [go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp] or [go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc] instead." A deprecation is declared by the author in the module's own REDACTED and applies to the whole module, not to one release, so moving to a newer version of it does not clear this. Follow the replacement the notice names.
D17 · Explicit Debt · XxxComment · ×1
  • XxxComment internal/proxy/dql/feature_usage_bench_test.go:38 — // go test ./internal/proxy/dql/ -run XXX -bench 'FeatureUsage' -benchtime 200000x — 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.
D20 · ADR Quality · Decision and consequences are present but trade-offs (e.g., etcd lease/lease timeout handling, index deletion consistency with MetaTable) are not stated in the visible portion · ×1
  • Decision and consequences are present but trade-offs (e.g., etcd lease/lease timeout handling, index deletion consistency with MetaTable) are not stated in the visible portion docs/design-docs/design_docs/20210731-index_design.md — Add a Consequences section covering trade-offs such as lease timeout recovery, index deletion vs. MetaTable consistency, and how to handle concurrent delete/delete requests
D20 · ADR Quality · Context/problem (the CreateCollection flow's motivation and why it matters) is absent in favor of only the execution path with proto code · ×1
  • Context/problem (the CreateCollection flow's motivation and why it matters) is absent in favor of only the execution path with proto code docs/design-docs/design_docs/20211217-milvus_create_collection.md — Add a brief Context section explaining what a Collection is (set of data like a Table), the problem it solves (data storage/sharding), and why this execution path exists over alternatives
D20 · ADR Quality · Decision and consequences are present but the context/problem is thin (only one sentence about ANNS efficiency vs accurate retrieval) and there are no trade-offs for using an approximate engine · ×1
  • Decision and consequences are present but the context/problem is thin (only one sentence about ANNS efficiency vs accurate retrieval) and there are no trade-offs for using an approximate engine docs/design-docs/design_docs/20211223-knowhere_design.md — Add a Context section explaining why approximate search is needed over exact retrieval for large datasets, then document the trade-offs: lower accuracy, potential ranking drift, and the acceptable error range.
D20 · ADR Quality · Context/problem and consequences/trade-offs are absent from the visible text · ×1
  • Context/problem and consequences/trade-offs are absent from the visible text docs/design-docs/design_docs/cdc/user_docs/02-cdc-replication-quick-start.md — Add a Context section explaining why CDC replication is needed (real-time data sync between clusters), an alternative model or trade-off for non-standby setups, and a Consequences section covering operational complexity, resource cost, and failover behavior
D20 · ADR Quality · No explicit decision and no consequences/trade-offs for the proposed TransformLog design (e.g. how ObserveMessage is handled, replay semantics) · ×1
  • No explicit decision and no consequences/trade-offs for the proposed TransformLog design (e.g. how ObserveMessage is handled, replay semantics) docs/design-docs/design_docs/wal/transformlog/transform_log.md — Add an explicit Decision section describing what TransformLog provides (ObserveMessage support, storage path) and its trade-offs (boundedness, latency, operator coupling)
D22 · Internal API Consistency · Inconsistent deserialization patterns. Some types use `from_json` with a single `Value` argument, while others use `from_json` with a `Map` and additional context arguments (like `helper`). `ResourceInfo` has two distinct methods `from_json` and `from_global_json` with different signatures, implying different parsing contexts that are not clearly distinguished by naming convention. · ×1
  • Inconsistent deserialization patterns. Some types use `from_json` with a single `Value` argument, while others use `from_json` with a `Map` and additional context arguments (like `helper`). `ResourceInfo` has two distinct methods `from_json` and `from_global_json` with different signatures, implying different parsing contexts that are not clearly distinguished by naming convention. — Standardize on a single deserialization pattern. If context is required, pass it as an optional argument or use a builder pattern. Rename `from_global_json` to something more descriptive if it serves a fundamentally different purpose, or unify the logic if it is just a variant of the same operation. (signatures: ResourceInfo.from_json(value: Value): Result | ResourceInfo.from_global_json(value: Value): Result | FileResourcePathHelper.from_json(value: Value): Result | GrpcTokenizer.from_json(params: Map): Result | JiebaTokenizer.from_json(params: Map, helper: FileResourcePathHelper): Result | LangIdentTokenizer.from_json(params: Map, helper: FileResourcePathHelper, fc): Result | LinderaTokenizer.from_json(params: Map, helper: FileResourcePathHelper): Result)
D22 · Internal API Consistency · Inconsistent naming for default instance retrieval. `LangIdentTokenizer` uses `default()` while `TantivyIndexVersion` uses `default_version()`. This creates ambiguity about whether `default()` is a static factory or an instance method (though signature suggests static), and breaks naming consistency across the API. · ×1
  • Inconsistent naming for default instance retrieval. `LangIdentTokenizer` uses `default()` while `TantivyIndexVersion` uses `default_version()`. This creates ambiguity about whether `default()` is a static factory or an instance method (though signature suggests static), and breaks naming consistency across the API. — Unify to `default()` or `default_instance()` across all types that provide a default configuration. (signatures: LangIdentTokenizer.default(): LangIdentTokenizer | TantivyIndexVersion.default_version(): Self)
D22 · Internal API Consistency · Inconsistent constructor signatures. Some tokenizers use `new()` with no arguments, while others require specific parameters. While this reflects different configuration needs, the lack of a unified builder or factory pattern makes the API feel fragmented. Specifically, `NgramTokenizerWithChars` returns a `Result` while others return the type directly, implying potential failure in construction that is not present in others. · ×1
  • Inconsistent constructor signatures. Some tokenizers use `new()` with no arguments, while others require specific parameters. While this reflects different configuration needs, the lack of a unified builder or factory pattern makes the API feel fragmented. Specifically, `NgramTokenizerWithChars` returns a `Result` while others return the type directly, implying potential failure in construction that is not present in others. — Consider a unified builder pattern or ensure that constructors either never fail (returning the type) or always fail (returning Result), or clearly document why some fail and others do not. (signatures: IcuTokenizer.new(): IcuTokenizer | ThaiTokenizer.new(): ThaiTokenizer | JiebaTokenizer.new(): JiebaTokenizer | LangIdentTokenizer.new(ident: BoxIdentifier): LangIdentTokenizer | NgramTokenizerWithChars.new(min_gram: usize, max_gram: usize, prefix_only: bool, token_chars_config: TokenCharsConfig): Result)
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Near-duplicate member pair (107 shared lines) · ×1
  • Near-duplicate member pair (107 shared lines) cmd/tools/binlogv2/minio_client.py:528 — cmd/tools/binlogv2/minio_client.py:528-684 | cmd/tools/binlogv2/minio_parquet_analyzer.py:639-800 — These two members are variants of one another: 107 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication · Near-duplicate member pair (46 shared lines) · ×1
  • Near-duplicate member pair (46 shared lines) tools/mgit.py:942 — tools/mgit.py:942-1013 | tools/mgit.py:1273-1369 — These two members are variants of one another: 46 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (5 members, 50+ identical tokens) cmd/tools/binlogv2/minio_client.py:294 — cmd/tools/binlogv2/minio_client.py:294-524 | cmd/tools/binlogv2/minio_parquet_analyzer.py:381-451 | cmd/tools/binlogv2/minio_parquet_analyzer.py:454-523 | cmd/tools/binlogv2/minio_parquet_analyzer.py:526-562 | cmd/tools/binlogv2/minio_parquet_analyzer.py:565-635 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication · Duplicated block (24–64 lines × 3) · ×1
  • Duplicated block (24–64 lines × 3) cmd/tools/binlogv2/minio_client.py:528 — cmd/tools/binlogv2/minio_client.py:528-591 | cmd/tools/binlogv2/minio_parquet_analyzer.py:639-696 | cmd/tools/binlogv2/parquet_analyzer_cli.py:50-73 — before extracting anything, compare `cmd/tools/binlogv2/minio_client.py` and `cmd/tools/binlogv2/minio_parquet_analyzer.py` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 315 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `cmd/tools/binlogv2/parquet_analyzer_cli.py:50` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `cmd/tools/binlogv2/minio_parquet_analyzer.py:699` calls `add_argument` and `cmd/tools/binlogv2/minio_client.py:596` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (55 lines × 2) · ×1
  • Duplicated block (55 lines × 2) cmd/tools/binlogv2/minio_client.py:93 — cmd/tools/binlogv2/minio_client.py:93-147 | cmd/tools/binlogv2/minio_parquet_analyzer.py:75-129 — before extracting anything, compare `cmd/tools/binlogv2/minio_client.py` and `cmd/tools/binlogv2/minio_parquet_analyzer.py` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 315 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (42 lines × 2) · ×1
  • Duplicated block (42 lines × 2) cmd/tools/binlogv2/minio_client.py:150 — cmd/tools/binlogv2/minio_client.py:150-191 | cmd/tools/binlogv2/minio_parquet_analyzer.py:132-173 — before extracting anything, compare `cmd/tools/binlogv2/minio_client.py` and `cmd/tools/binlogv2/minio_parquet_analyzer.py` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 315 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 (36 lines × 2) · ×1
  • Duplicated block (36 lines × 2) cmd/tools/binlogv2/parquet_analyzer/vector_deserializer.py:187 — cmd/tools/binlogv2/parquet_analyzer/vector_deserializer.py:187-222 | cmd/tools/binlogv2/parquet_analyzer/vector_deserializer.py:226-261 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (19–28 lines × 2) · ×1
  • Duplicated block (19–28 lines × 2) cmd/tools/binlogv2/minio_client.py:30 — cmd/tools/binlogv2/minio_client.py:30-57 | cmd/tools/binlogv2/minio_parquet_analyzer.py:31-49 — before extracting anything, compare `cmd/tools/binlogv2/minio_client.py` and `cmd/tools/binlogv2/minio_parquet_analyzer.py` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 315 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `port` to `int = 9001` in one and `int = 9000` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (24–28 lines × 2) · ×1
  • Duplicated block (24–28 lines × 2) tools/mgit.py:535 — tools/mgit.py:535-562 | tools/mgit.py:829-852 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `tools/mgit.py:535` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (27 lines × 2) · ×1
  • Duplicated block (27 lines × 2) cmd/tools/binlogv2/parquet_analyzer/analyzer.py:75 — cmd/tools/binlogv2/parquet_analyzer/analyzer.py:75-101 | cmd/tools/binlogv2/parquet_analyzer/analyzer.py:103-129 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (21–23 lines × 2) · ×1
  • Duplicated block (21–23 lines × 2) tools/mgit.py:667 — tools/mgit.py:667-689 | tools/mgit.py:698-718 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (22 lines × 2) · ×1
  • Duplicated block (22 lines × 2) cmd/tools/binlogv2/minio_client.py:613 — cmd/tools/binlogv2/minio_client.py:613-634 | cmd/tools/binlogv2/minio_parquet_analyzer.py:719-740 — before extracting anything, compare `cmd/tools/binlogv2/minio_client.py` and `cmd/tools/binlogv2/minio_parquet_analyzer.py` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 315 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (20 lines × 2) · ×1
  • Duplicated block (20 lines × 2) cmd/tools/binlogv2/minio_client.py:641 — cmd/tools/binlogv2/minio_client.py:641-660 | cmd/tools/binlogv2/minio_parquet_analyzer.py:747-766 — before extracting anything, compare `cmd/tools/binlogv2/minio_client.py` and `cmd/tools/binlogv2/minio_parquet_analyzer.py` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 315 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 (18–20 lines × 2) · ×1
  • Duplicated block (18–20 lines × 2) tools/mgit.py:2607 — tools/mgit.py:2607-2624 | tools/mgit.py:3531-3550 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `tools/mgit.py:3553` calls `get_upstream_master` and `tools/mgit.py:2627` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (19 lines × 3) · ×1
  • Duplicated block (19 lines × 3) cmd/tools/binlogv2/minio_parquet_analyzer.py:472 — cmd/tools/binlogv2/minio_parquet_analyzer.py:472-490 | cmd/tools/binlogv2/minio_parquet_analyzer.py:530-548 | cmd/tools/binlogv2/minio_parquet_analyzer.py:587-605 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (16–18 lines × 4) · ×1
  • Duplicated block (16–18 lines × 4) tools/mgit.py:965 — tools/mgit.py:965-982 | tools/mgit.py:984-999 | tools/mgit.py:1309-1326 | tools/mgit.py:1332-1347 — 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (18 lines × 2) · ×1
  • Duplicated block (18 lines × 2) cmd/tools/binlogv2/minio_client.py:294 — cmd/tools/binlogv2/minio_client.py:294-311 | cmd/tools/binlogv2/minio_parquet_analyzer.py:381-398 — before extracting anything, compare `cmd/tools/binlogv2/minio_client.py` and `cmd/tools/binlogv2/minio_parquet_analyzer.py` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 315 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×1
  • Duplicated block (17 lines × 2) tools/mgit.py:2261 — tools/mgit.py:2261-2277 | tools/mgit.py:2291-2307 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `tools/mgit.py:2290` calls `join` and `tools/mgit.py:2260` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (15–17 lines × 2) · ×1
  • Duplicated block (15–17 lines × 2) tools/mgit.py:2376 — tools/mgit.py:2376-2390 | tools/mgit.py:2421-2437 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×1
  • Duplicated block (15 lines × 2) cmd/tools/binlogv2/minio_client.py:208 — cmd/tools/binlogv2/minio_client.py:208-222 | cmd/tools/binlogv2/minio_parquet_analyzer.py:245-259 — before extracting anything, compare `cmd/tools/binlogv2/minio_client.py` and `cmd/tools/binlogv2/minio_parquet_analyzer.py` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 315 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (12–15 lines × 2) · ×1
  • Duplicated block (12–15 lines × 2) tools/mgit.py:2114 — tools/mgit.py:2114-2125 | tools/mgit.py:2467-2481 — 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 × 4) · ×1
  • Duplicated block (14 lines × 4) cmd/tools/binlogv2/minio_client.py:309 — cmd/tools/binlogv2/minio_client.py:309-322 | cmd/tools/binlogv2/minio_client.py:424-437 | cmd/tools/binlogv2/minio_parquet_analyzer.py:396-409 | cmd/tools/binlogv2/minio_parquet_analyzer.py:456-469 — before extracting anything, compare `cmd/tools/binlogv2/minio_client.py` and `cmd/tools/binlogv2/minio_parquet_analyzer.py` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 315 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (4–13 lines × 3) · ×1
  • Duplicated block (4–13 lines × 3) cmd/tools/binlogv2/parquet_analyzer/analyzer.py:192 — cmd/tools/binlogv2/parquet_analyzer/analyzer.py:192-195 | cmd/tools/binlogv2/parquet_analyzer_cli.py:126-138 | cmd/tools/binlogv2/parquet_analyzer_cli.py:223-235 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×1
  • Duplicated block (13 lines × 2) tools/mgit.py:2274 — tools/mgit.py:2274-2286 | tools/mgit.py:2380-2392 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (8–9 lines × 6) · ×1
  • Duplicated block (8–9 lines × 6) cmd/tools/binlogv2/minio_client.py:309 — cmd/tools/binlogv2/minio_client.py:309-316 | cmd/tools/binlogv2/minio_client.py:424-431 | cmd/tools/binlogv2/minio_parquet_analyzer.py:396-403 | cmd/tools/binlogv2/minio_parquet_analyzer.py:477-485 | cmd/tools/binlogv2/minio_parquet_analyzer.py:535-543 | cmd/tools/binlogv2/minio_parquet_analyzer.py:592-600 — before extracting anything, compare `cmd/tools/binlogv2/minio_client.py` and `cmd/tools/binlogv2/minio_parquet_analyzer.py` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 315 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (9 lines × 4) · ×1
  • Duplicated block (9 lines × 4) cmd/tools/binlogv2/minio_client.py:447 — cmd/tools/binlogv2/minio_client.py:447-455 | cmd/tools/binlogv2/minio_parquet_analyzer.py:473-481 | cmd/tools/binlogv2/minio_parquet_analyzer.py:531-539 | cmd/tools/binlogv2/minio_parquet_analyzer.py:588-596 — before extracting anything, compare `cmd/tools/binlogv2/minio_client.py` and `cmd/tools/binlogv2/minio_parquet_analyzer.py` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 315 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×1
  • Duplicated block (8 lines × 2) cmd/tools/binlogv2/parquet_analyzer/analyzer.py:182 — cmd/tools/binlogv2/parquet_analyzer/analyzer.py:182-189 | cmd/tools/binlogv2/parquet_analyzer_cli.py:222-229 — 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 × 3) · ×1
  • Duplicated block (6 lines × 3) tools/mgit.py:690 — tools/mgit.py:690-695 | tools/mgit.py:720-725 | tools/mgit.py:746-751 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×1
  • Duplicated block (5 lines × 2) cmd/tools/binlogv2/parquet_analyzer/meta_parser.py:388 — cmd/tools/binlogv2/parquet_analyzer/meta_parser.py:388-392 | cmd/tools/binlogv2/parquet_analyzer_cli.py:157-161 — 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.
D6 · Cohesion (LCOM4) · Low cohesion · ×1
  • Low cohesion: _CppLintState (LCOM4 4) internal/core/build-support/cpplint.py:1245 — _CppLintState's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
P7 · Outbound HTTP resilience · Outbound HTTP without resilience · ×1
  • Outbound HTTP without resilience REDACTED:427 — `http.Client{` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
X12 · Unreachable branch · Branch is unreachable · ×1
  • Branch is unreachable — an earlier arm already matches it cmd/tools/binlogv2/parquet_analyzer/vector_deserializer.py:65 — `"bfloat16" in field_name.lower()` can only be reached when `"float16" in field_name.lower()` on line 63 was false — but every string satisfying the first satisfies the second, so this `elif` never runs. Test the more specific literal `"bfloat16"` BEFORE the more general `"float16"`, or make the arms mutually exclusive.
X2 · Cancellation propagation · Function without context.Context · ×1
  • Function without context.Context: GetConn internal/util/function/models/zilliz/zilliz_client.go:91 — `GetConn` calls `grpc.DialContext(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`.
Minor — 803 finding(s)
D29 · Static Analysis (SAST) · REDACTED · ×504
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 479 more in this group — see findings.md.
D34 · Knowledge Freshness · Orphaned file · ×64
  • Orphaned file pkg/mq/msgstream/msg_for_user_role.go:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file cmd/tools/migration/backend/etcd210.go:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file cmd/tools/migration/meta/210_to_220.go:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file pkg/util/typeutil/gen_empty_field_data.go:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file pkg/mq/msgstream/msg_for_collection.go:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file cmd/tools/migration/meta/meta220.go:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file cmd/tools/migration/meta/meta210.go:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file pkg/mq/msgstream/mqwrapper/kafka/kafka_consumer.go:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file pkg/util/metricsinfo/metric_request.go:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file pkg/util/metricsinfo/utils.go:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file cmd/tools/config-docs-generator/main.go:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file pkg/mq/msgstream/unmarshal.go:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file internal/parser/planparserv2/show_visitor.go:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file pkg/util/resource/resource_manager.go:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file internal/util/quota/quota_constant.go:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file internal/querynodev2/pipeline/manager.go:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file internal/core/build-support/run_clang_format.py:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file pkg/mq/msgstream/msg_for_index.go:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file internal/rootcoord/scheduler.go:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file pkg/util/funcutil/policy.go:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file pkg/mq/msgstream/mqwrapper/rmq/rmq_client.go:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file pkg/util/funcutil/parallel.go:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file pkg/mq/msgstream/msg_for_database.go:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • + 39 more in this group — see findings.md.
D20 · ADR Quality · ADR has no Decision and Consequences section · ×54
  • ADR has no Decision and Consequences section docs/design-docs/design_docs/20220725-dynamic-config.md:1 — docs/design-docs/design_docs/20220725-dynamic-config.md has no Decision and Consequences section (a heading such as `## Decision`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Decision and Consequences section docs/design-docs/design_docs/20260129-search-orderby.md:1 — docs/design-docs/design_docs/20260129-search-orderby.md has no Decision and Consequences section (a heading such as `## Decision`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Decision and Consequences section docs/design-docs/design_docs/20260131-client_side_telemetry.md:1 — docs/design-docs/design_docs/20260131-client_side_telemetry.md has no Decision and Consequences section (a heading such as `## Decision`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Decision and Consequences section docs/design-docs/design_docs/20260203-query-orderby.md:1 — docs/design-docs/design_docs/20260203-query-orderby.md has no Decision and Consequences section (a heading such as `## Decision`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Decision and Consequences section docs/design-docs/design_docs/20260204-channel_exclusive_mode.md:1 — docs/design-docs/design_docs/20260204-channel_exclusive_mode.md has no Decision and Consequences section (a heading such as `## Decision`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Decision and Consequences section docs/design-docs/design_docs/20260209-pinyin_filter.md:1 — docs/design-docs/design_docs/20260209-pinyin_filter.md has no Decision and Consequences section (a heading such as `## Decision`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Decision and Consequences section docs/design-docs/design_docs/20260226-manifest-format.md:1 — docs/design-docs/design_docs/20260226-manifest-format.md has no Decision and Consequences section (a heading such as `## Decision`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Decision and Consequences section docs/design-docs/design_docs/20260227-yc-text-embedding-provider.md:1 — docs/design-docs/design_docs/20260227-yc-text-embedding-provider.md has no Decision and Consequences section (a heading such as `## Decision`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Decision and Consequences section docs/design-docs/design_docs/20260305-local_format.md:1 — docs/design-docs/design_docs/20260305-local_format.md has no Decision and Consequences section (a heading such as `## Decision`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Decision and Consequences section docs/design-docs/design_docs/20260313-scalar_index_version_management.md:1 — docs/design-docs/design_docs/20260313-scalar_index_version_management.md has no Decision and Consequences section (a heading such as `## Decision`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Decision and Consequences section docs/design-docs/design_docs/20260324-segment_filter_pk_predicate_pruning.md:1 — docs/design-docs/design_docs/20260324-segment_filter_pk_predicate_pruning.md has no Decision and Consequences section (a heading such as `## Decision`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Decision and Consequences section docs/design-docs/design_docs/20260407-text_lob_storage.md:1 — docs/design-docs/design_docs/20260407-text_lob_storage.md has no Decision and Consequences section (a heading such as `## Decision`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Decision and Consequences section docs/design-docs/design_docs/20260409-regex_filter.md:1 — docs/design-docs/design_docs/20260409-regex_filter.md has no Decision and Consequences section (a heading such as `## Decision`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Decision and Consequences section docs/design-docs/design_docs/20260410-json_path_index_multi_type.md:1 — docs/design-docs/design_docs/20260410-json_path_index_multi_type.md has no Decision and Consequences section (a heading such as `## Decision`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Decision and Consequences section docs/design-docs/design_docs/20260521-external-table-function-output.md:1 — docs/design-docs/design_docs/20260521-external-table-function-output.md has no Decision and Consequences section (a heading such as `## Decision`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Decision and Consequences section docs/design-docs/design_docs/20260601-rbac-user-description.md:1 — docs/design-docs/design_docs/20260601-rbac-user-description.md has no Decision and Consequences section (a heading such as `## Decision`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Decision and Consequences section docs/design-docs/design_docs/20260602-expression-result-cache.md:1 — docs/design-docs/design_docs/20260602-expression-result-cache.md has no Decision and Consequences section (a heading such as `## Decision`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Decision and Consequences section docs/design-docs/design_docs/20260603-target-basecompaction.md:1 — docs/design-docs/design_docs/20260603-target-basecompaction.md has no Decision and Consequences section (a heading such as `## Decision`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Decision and Consequences section docs/design-docs/design_docs/20260604-idempotent_write.md:1 — docs/design-docs/design_docs/20260604-idempotent_write.md has no Decision and Consequences section (a heading such as `## Decision`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Decision and Consequences section docs/design-docs/design_docs/20260609-external-snapshot-export-restore.md:1 — docs/design-docs/design_docs/20260609-external-snapshot-export-restore.md has no Decision and Consequences section (a heading such as `## Decision`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Decision and Consequences section docs/design-docs/design_docs/20260610-shard_split.md:1 — docs/design-docs/design_docs/20260610-shard_split.md has no Decision and Consequences section (a heading such as `## Decision`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Decision and Consequences section docs/design-docs/design_docs/20260620-bitwise-filter-operators.md:1 — docs/design-docs/design_docs/20260620-bitwise-filter-operators.md has no Decision and Consequences section (a heading such as `## Decision`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Decision and Consequences section docs/design-docs/design_docs/20260624-function-chain-api.md:1 — docs/design-docs/design_docs/20260624-function-chain-api.md has no Decision and Consequences section (a heading such as `## Decision`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Decision and Consequences section docs/design-docs/design_docs/20260702-text_match_fuzzy.md:1 — docs/design-docs/design_docs/20260702-text_match_fuzzy.md has no Decision and Consequences section (a heading such as `## Decision`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Decision and Consequences section docs/design-docs/design_docs/20260703-bitwise-shift-and-not-operators.md:1 — docs/design-docs/design_docs/20260703-bitwise-shift-and-not-operators.md has no Decision and Consequences section (a heading such as `## Decision`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • + 29 more in this group — see findings.md.
D31 · IaC & Container Security · Low IaC · ×49
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 24 more in this group — see findings.md.
M4 · Documentation accuracy · README/code drift · ×40
  • README/code drift README.md:85 — README advertises a microservices architecture, but the repo is a single project with no service manifests — searched for: `microservice`, `service-mesh`, `istio`. Each was matched case- and separator-insensitively against file and directory NAMES anywhere in the tree, and against the CONTENTS of manifest and configuration files (package.json and other *.json, *.csproj, *.props, *.sln/*.slnx, *.yml, *.toml, *.config, tool configs such as eslint.config.js, REDACTED); the README's own prose never counts, so a claim is never refuted by merely being made. Nothing outside that search was read — a footprint living only in a submodule, in a file type not listed here, or under a name none of those terms matches is not seen, and this row is then wrong.
  • README/code drift docs/dev/README.md:10 — docs/dev/README.md names `docs/developer_guides/`, but no file or folder `docs/developer_guides` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/dev/error_handling_casebook.md:95 — docs/dev/error_handling_casebook.md names `internal/proxy/search_reduce_util.go`, but no file or folder `internal/proxy/search_reduce_util.go` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift tests/integration/README.md:43 — tests/integration/README.md changes into `[milvus-folder]/deployments/docker/dev`, but no such folder exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift deployments/monitor/grafana/README.md:5 — deployments/monitor/grafana/README.md links to `monitor_overview.md`, but `deployments/monitor/grafana/monitor_overview.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/agent_guides/observability/logging.md:3 — docs/agent_guides/observability/logging.md names `github.com/milvus-io/milvus/pkg/v3/mlog`, but no file or folder `github.com/milvus-io/milvus/pkg/v3/mlog` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/design-docs/design_docs/20211214-milvus_hybrid_ts.md:3 — docs/design-docs/design_docs/20211214-milvus_hybrid_ts.md links to `./milvus_timesync_en.md`, but `docs/design-docs/design_docs/milvus_timesync_en.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/design-docs/design_docs/20260105-external_table.md:164 — docs/design-docs/design_docs/20260105-external_table.md names `milvus.proto`, but no file or folder `milvus.proto` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/design-docs/design_docs/20260105-external_table.md:409 — docs/design-docs/design_docs/20260105-external_table.md names `internal/proxy/task.go`, but no file or folder `internal/proxy/task.go` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/design-docs/design_docs/20260105-external_table.md:426 — docs/design-docs/design_docs/20260105-external_table.md names `schema.proto`, but no file or folder `schema.proto` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/design-docs/design_docs/20260105-external_table.md:590 — docs/design-docs/design_docs/20260105-external_table.md names `internal/proxy/task_insert.go`, but no file or folder `internal/proxy/task_insert.go` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/design-docs/design_docs/20260105-external_table.md:591 — docs/design-docs/design_docs/20260105-external_table.md names `internal/proxy/task_delete.go`, but no file or folder `internal/proxy/task_delete.go` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/design-docs/design_docs/20260105-external_table.md:592 — docs/design-docs/design_docs/20260105-external_table.md names `internal/proxy/task_upsert.go`, but no file or folder `internal/proxy/task_upsert.go` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/design-docs/design_docs/20260105-external_table.md:593 — docs/design-docs/design_docs/20260105-external_table.md names `internal/proxy/task_import.go`, but no file or folder `internal/proxy/task_import.go` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/design-docs/design_docs/20260105-external_table.md:594 — docs/design-docs/design_docs/20260105-external_table.md names `internal/proxy/task_flush.go`, but no file or folder `internal/proxy/task_flush.go` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/design-docs/design_docs/20260129-add-function-field-design.md:198 — docs/design-docs/design_docs/20260129-add-function-field-design.md names `internal/proxy/task.go`, but no file or folder `internal/proxy/task.go` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/design-docs/design_docs/20260129-add-function-field-design.md:391 — docs/design-docs/design_docs/20260129-add-function-field-design.md names `internal/datacoord/compaction_policy_backfill.go`, but no file or folder `internal/datacoord/compaction_policy_backfill.go` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/design-docs/design_docs/20260129-add-function-field-design.md:466 — docs/design-docs/design_docs/20260129-add-function-field-design.md names `internal/datanode/compactor/backfill_compactor.go`, but no file or folder `internal/datanode/compactor/backfill_compactor.go` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/design-docs/design_docs/20260129-add-function-field-design.md:524 — docs/design-docs/design_docs/20260129-add-function-field-design.md names `internal/querynodev2/pipeline/embedding_node.go`, but no file or folder `internal/querynodev2/pipeline/embedding_node.go` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/design-docs/design_docs/20260129-add-function-field-design.md:658 — docs/design-docs/design_docs/20260129-add-function-field-design.md names `internal/util/schema_util.go`, but no file or folder `internal/util/schema_util.go` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/design-docs/design_docs/20260129-add-function-field-design.md:997 — docs/design-docs/design_docs/20260129-add-function-field-design.md names `internal/util/schema_util_test.go`, but no file or folder `internal/util/schema_util_test.go` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/design-docs/design_docs/20260129-add-function-field-design.md:998 — docs/design-docs/design_docs/20260129-add-function-field-design.md names `internal/datacoord/compaction_policy_backfill_test.go`, but no file or folder `internal/datacoord/compaction_policy_backfill_test.go` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/design-docs/design_docs/20260129-add-function-field-design.md:999 — docs/design-docs/design_docs/20260129-add-function-field-design.md names `internal/datacoord/compaction_task_backfill_test.go`, but no file or folder `internal/datacoord/compaction_task_backfill_test.go` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/design-docs/design_docs/20260129-add-function-field-design.md:1000 — docs/design-docs/design_docs/20260129-add-function-field-design.md names `internal/datanode/compactor/backfill_compactor_test.go`, but no file or folder `internal/datanode/compactor/backfill_compactor_test.go` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/design-docs/design_docs/20260129-add-function-field-design.md:1037 — docs/design-docs/design_docs/20260129-add-function-field-design.md links to `../architecture.md`, but `docs/design-docs/architecture.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • + 15 more in this group — see findings.md.
X10 · Duplicated predicate · Duplicated predicate · ×25
  • Duplicated predicate pkg/rules.go:420 — `!m.File().Name.Matches(`_test\.go$`) && !m.File().Name.Matches(`test_streaming\.go$`) && !m.File().PkgPath.Matches(`/milvus/cmd/`) && !m.Fil…` appears character-identically in 2 files — pkg/rules.go, rules.go. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate pkg/rules.go:461 — `!m.File().Name.Matches(`_test\.go$`) && !m.File().PkgPath.Matches(`/milvus/cmd/`) && !m.File().PkgPath.Matches(`/milvus/tests/`) && !m.File(…` appears character-identically in 2 files — pkg/rules.go, rules.go. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate internal/querynodev2/delegator/delegator.go:1450 — `!merr.IsMilvusError(err) || merr.IsRetryableErr(err)` appears character-identically in 2 files — internal/querynodev2/delegator/delegator.go, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate internal/proxy/shardclient/look_aside_balancer.go:115 — `!ok || !targetMetrics.unavailable.Load()` appears character-identically in 2 files — internal/proxy/shardclient/look_aside_balancer.go, internal/proxy/shardclient/refined_look_aside_balancer.go. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate internal/util/importutilv2/binlog/snapshot_bitmap.go:140 — `!ok || timestamps.Len() != record.Len() || timestamps.NullN() != 0` appears character-identically in 2 files — internal/util/importutilv2/binlog/snapshot_bitmap.go, internal/util/importutilv2/binlog/snapshot_delete.go. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate internal/proxy/dml/util_dml.go:664 — `!sf.GetNullable() && !seenStructs[sf.Name]` appears character-identically in 2 files — internal/proxy/dml/util_dml.go, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate REDACTED:66 — `!typeutil.IsAutoPKField(field) && field.GetName() != dynamicField.GetName()` appears character-identically in 2 files — REDACTED, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate internal/proxy/ddl/util_ddl.go:89 — `(c < 'A' || c > 'Z') && (c < 'a' || c > 'z')` appears character-identically in 2 files — internal/proxy/ddl/util_ddl.go, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate internal/rootcoord/ddl_callbacks_alter_collection_add_struct_field.go:268 — `(c >= 'A' && c <= 'Z') || (c >= 'a' && c <= 'z')` appears character-identically in 2 files — internal/rootcoord/ddl_callbacks_alter_collection_add_struct_field.go, internal/util/indexparamcheck/index_params_validation.go. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate pkg/mq/msgstream/mqwrapper/kafka/kafka_client.go:88 — `(config.SaslUsername.GetValue() == "" && config.SaslPassword.GetValue() != "") || (config.SaslUsername.GetValue() != "" && config.SaslPasswo…` appears character-identically in 2 files — pkg/mq/msgstream/mqwrapper/kafka/kafka_client.go, pkg/streaming/walimpls/impls/kafka/builder.go. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate internal/proxy/dql/task_query.go:926 — `NamespacePartitionKeyMode(t.schema.CollectionSchema) && t.request.Namespace != nil` appears character-identically in 2 files — internal/proxy/dql/task_query.go, internal/proxy/dql/task_search.go. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate internal/proxy/dql/task_query.go:1059 — `NamespacePartitionKeyModeEnabled(t.schema.CollectionSchema) && t.request.Namespace != nil` appears character-identically in 2 files — internal/proxy/dql/task_query.go, internal/proxy/dql/task_search.go. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate REDACTED:312 — `base.Scheme != "http" && base.Scheme != "https"` appears character-identically in 2 files — REDACTED, internal/util/function/models/vllm/vllm_client.go. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate internal/proxy/ddl/util_ddl.go:947 — `c != '_' && !isAlpha(c) && !isNumber(c) && !strings.ContainsRune(allowedChars, rune(c))` appears character-identically in 2 files — internal/proxy/ddl/util_ddl.go, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate internal/proxy/ddl/util_ddl.go:195 — `c != '_' && !isAlpha(c) && !isNumber(c) && c != '-'` appears character-identically in 3 files — internal/proxy/ddl/util_ddl.go, internal/proxy/dql/util_dql.go, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate REDACTED:159 — `c.field.GetNullable() || c.field.GetDefaultValue() != nil` appears character-identically in 2 files — REDACTED, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate internal/querycoordv2/checkers/channel_checker.go:90 — `c.targetMgr.IsNextTargetExist(ctx, collectionID) || c.targetMgr.IsCurrentTargetExist(ctx, collectionID, common.AllPartitionsID)` appears character-identically in 2 files — internal/querycoordv2/checkers/channel_checker.go, internal/querycoordv2/checkers/segment_checker.go. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate REDACTED:78 — `cg.columns == nil && cg.num_of_columns > 0` appears character-identically in 2 files — REDACTED, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate REDACTED:480 — `cgroups.column_group_array == nil && cgroups.num_of_column_groups > 0` appears character-identically in 2 files — REDACTED, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate internal/querycoordv2/checkers/balance_checker.go:245 — `collection != nil && collection.GetStatus() == querypb.LoadStatus_Loaded` appears character-identically in 2 files — internal/querycoordv2/checkers/balance_checker.go, internal/querycoordv2/utils/util.go. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate internal/datacoord/external_collection_refresh_checker.go:406 — `collection == nil || collection.Schema == nil` appears character-identically in 4 files — internal/datacoord/external_collection_refresh_checker.go, internal/datacoord/import_v3_schema.go, internal/datacoord/manifest_index.go, internal/datacoord/segment_readiness.go. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate pkg/mq/msgstream/mqwrapper/kafka/kafka_client.go:101 — `config.SaslUsername.GetValue() != "" && config.SaslPassword.GetValue() != ""` appears character-identically in 2 files — pkg/mq/msgstream/mqwrapper/kafka/kafka_client.go, pkg/streaming/walimpls/impls/kafka/builder.go. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate internal/proxy/dql/task_query.go:987 — `consistencyLevel == 0 && guaranteeTs > 0` appears character-identically in 2 files — internal/proxy/dql/task_query.go, internal/proxy/dql/task_search.go. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate internal/datacoord/compaction_task_l0.go:599 — `current == nil || !isSegmentHealthy(current)` appears character-identically in 2 files — internal/datacoord/compaction_task_l0.go, internal/datacoord/task_stats.go. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate internal/datacoord/meta.go:2010 — `current == nil || current.GetState() == commonpb.SegmentState_Dropped` appears character-identically in 2 files — internal/datacoord/meta.go, internal/datacoord/task_refresh_external_collection.go. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
D20 · ADR Quality · ADR lacks an enforcement field · ×15
  • ADR lacks an enforcement field docs/design-docs/design_docs/wal/broadcast_ack_module.md:1 — Add an `enforcement:` frontmatter field or a plain `Enforcement:` header line (prose/test/analyzer/not-applicable) to make the rung explicit — the other ADRs in this repo already declare one.
  • ADR lacks an enforcement field docs/design-docs/design_docs/wal/checkpoint-persistence.md:1 — Add an `enforcement:` frontmatter field or a plain `Enforcement:` header line (prose/test/analyzer/not-applicable) to make the rung explicit — the other ADRs in this repo already declare one.
  • ADR lacks an enforcement field docs/design-docs/design_docs/wal/l0_materializer.md:1 — Add an `enforcement:` frontmatter field or a plain `Enforcement:` header line (prose/test/analyzer/not-applicable) to make the rung explicit — the other ADRs in this repo already declare one.
  • ADR lacks an enforcement field docs/design-docs/design_docs/wal/local_flush_control.md:1 — Add an `enforcement:` frontmatter field or a plain `Enforcement:` header line (prose/test/analyzer/not-applicable) to make the rung explicit — the other ADRs in this repo already declare one.
  • ADR lacks an enforcement field docs/design-docs/design_docs/wal/message-workflow.md:1 — Add an `enforcement:` frontmatter field or a plain `Enforcement:` header line (prose/test/analyzer/not-applicable) to make the rung explicit — the other ADRs in this repo already declare one.
  • ADR lacks an enforcement field docs/design-docs/design_docs/wal/message_ack.md:1 — Add an `enforcement:` frontmatter field or a plain `Enforcement:` header line (prose/test/analyzer/not-applicable) to make the rung explicit — the other ADRs in this repo already declare one.
  • ADR lacks an enforcement field docs/design-docs/design_docs/wal/message_body_cache.md:1 — Add an `enforcement:` frontmatter field or a plain `Enforcement:` header line (prose/test/analyzer/not-applicable) to make the rung explicit — the other ADRs in this repo already declare one.
  • ADR lacks an enforcement field docs/design-docs/design_docs/wal/recovery-tail-controller.md:1 — Add an `enforcement:` frontmatter field or a plain `Enforcement:` header line (prose/test/analyzer/not-applicable) to make the rung explicit — the other ADRs in this repo already declare one.
  • ADR lacks an enforcement field docs/design-docs/design_docs/wal/segment_view_module.md:1 — Add an `enforcement:` frontmatter field or a plain `Enforcement:` header line (prose/test/analyzer/not-applicable) to make the rung explicit — the other ADRs in this repo already declare one.
  • ADR lacks an enforcement field docs/design-docs/design_docs/wal/streamingnode_vchannel_wal_view.md:1 — Add an `enforcement:` frontmatter field or a plain `Enforcement:` header line (prose/test/analyzer/not-applicable) to make the rung explicit — the other ADRs in this repo already declare one.
  • ADR lacks an enforcement field docs/design-docs/design_docs/wal/summary_l0_materializer.md:1 — Add an `enforcement:` frontmatter field or a plain `Enforcement:` header line (prose/test/analyzer/not-applicable) to make the rung explicit — the other ADRs in this repo already declare one.
  • ADR lacks an enforcement field docs/design-docs/design_docs/wal/transform_log.md:1 — Add an `enforcement:` frontmatter field or a plain `Enforcement:` header line (prose/test/analyzer/not-applicable) to make the rung explicit — the other ADRs in this repo already declare one.
  • ADR lacks an enforcement field docs/design-docs/design_docs/wal/transform_log_view_module.md:1 — Add an `enforcement:` frontmatter field or a plain `Enforcement:` header line (prose/test/analyzer/not-applicable) to make the rung explicit — the other ADRs in this repo already declare one.
  • ADR lacks an enforcement field docs/design-docs/design_docs/wal/vchannel_view_module.md:1 — Add an `enforcement:` frontmatter field or a plain `Enforcement:` header line (prose/test/analyzer/not-applicable) to make the rung explicit — the other ADRs in this repo already declare one.
  • ADR lacks an enforcement field docs/design-docs/design_docs/wal/wal-recovery-architecture.md:1 — Add an `enforcement:` frontmatter field or a plain `Enforcement:` header line (prose/test/analyzer/not-applicable) to make the rung explicit — the other ADRs in this repo already declare one.
D41 · Kernel & Syscall Confinement · No seccomp profile · ×13
  • No seccomp profile REDACTED:2 — The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
  • No seccomp profile build/ci/jenkins/pod/scale-test.yaml:2 — The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
  • No seccomp profile REDACTED:10 — The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
  • No seccomp profile REDACTED:272 — The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
  • No seccomp profile REDACTED:351 — The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
  • No seccomp profile REDACTED:114 — The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
  • No seccomp profile REDACTED:2 — The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
  • No seccomp profile REDACTED:2 — The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
  • No seccomp profile REDACTED:2 — The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
  • No seccomp profile REDACTED:2 — The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
  • No seccomp profile REDACTED:2 — The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
  • No seccomp profile REDACTED:2 — The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
  • No seccomp profile REDACTED:2 — The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
D16 · Bus Factor · Off-boarding risk · ×6
  • Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 28 significant file(s) lose their only recent owner: pkg/streaming/util/message/codegen/main.go, internal/coordinator/restful_replica.go, REDACTED, internal/streamingnode/client/handler/producer/producer_impl.go, pkg/streaming/util/message/marshal_log_object.go, internal/streamingnode/server/wal/interceptors/wab/write_ahead_buffer.go, internal/util/streamingutil/service/discoverer/session_discoverer.go, REDACTED (+20 more). Pair on, review, or document these before any departure.
  • Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 18 significant file(s) lose their only recent owner: internal/querynodev2/tasks/heap_merge_reduce.go, internal/util/function/chain/repr.go, internal/util/function/chain/operator_group_by.go, internal/util/function/chain/chain.go, internal/util/function/chain/expr/num_combine_expr.go, internal/querynodev2/tasks/l1_function_chain.go, REDACTED, internal/util/function/chain/operator_sort.go (+10 more). Pair on, review, or document these before any departure.
  • Off-boarding risk: anonymized user #3 — If anonymized user #3 becomes unavailable, 15 significant file(s) lose their only recent owner: tools/mgit.py, internal/rootcoord/telemetry/manager.go, client/membership/sbbf/sbbf.go, internal/util/grpcclient/compression.go, client/membership/roaringfilter/roaring_filter.go, internal/util/grpcclient/compression_zstd.go, pkg/util/fastpb/helpers.go, internal/proxy/telemetry_models.go (+7 more). Pair on, review, or document these before any departure.
  • Off-boarding risk: anonymized user #4 — If anonymized user #4 becomes unavailable, 4 significant file(s) lose their only recent owner: internal/metastore/model/segment_change_group.go, client/milvusclient/iterator.go, client/milvusclient/resource_group.go, internal/proxy/dml/task_batch_update_manifest.go. Pair on, review, or document these before any departure.
  • Off-boarding risk: anonymized user #5 — If anonymized user #5 becomes unavailable, 3 significant file(s) lose their only recent owner: client/milvusclient/snapshot_options.go, pkg/util/externalspec/specutil/spec.go, REDACTED. Pair on, review, or document these before any departure.
  • Off-boarding risk: anonymized user #6 — If anonymized user #6 becomes unavailable, 3 significant file(s) lose their only recent owner: internal/proxy/accesslog/global.go, REDACTED, internal/util/function/local_store.go. Pair on, review, or document these before any departure.
D7 · Architectural Integrity · Checkable ADR rule enforced only by prose · ×6
  • Checkable ADR rule enforced only by prose: MEP: PyUDF FunctionChain Worker Pool docs/design-docs/design_docs/20260722-pyudf-function-chain.md — ADR 'MEP: PyUDF FunctionChain Worker Pool' declares `enforcement: prose` but states a rule a test or analyzer can check: "it does not mean that Python imports succeeded, workers are listening, resources are synchronized, or a user model is loaded." Nothing in the build fails when the code breaks it — add an architecture test or analyzer (and `enforcement: test|analyzer` with an `enforcement_link`).
  • Checkable ADR rule enforced only by prose: Hybrid Search Function Chain Integration docs/design-docs/design_docs/20260818-hybrid-search-function-chain.md — ADR 'Hybrid Search Function Chain Integration' declares `enforcement: prose` but states a rule a test or analyzer can check: "Raw-RPC stage/cardinality/rerank-source validation, so server coverage does not depend on the skipped SDK-specific Hybrid tests." Nothing in the build fails when the code breaks it — add an architecture test or analyzer (and `enforcement: test|analyzer` with an `enforcement_link`).
  • Checkable ADR rule enforced only by prose: Compaction Data-Integrity E2E Design docs/design-docs/design_docs/compaction_data_integrity_e2e_design.md — ADR 'Compaction Data-Integrity E2E Design' declares `enforcement: prose` but states a rule a test or analyzer can check: "The import file may be internally chunked for manageable generation and upload, but the test does not require a fixed number of import tasks or physical segments." Nothing in the build fails when the code breaks it — add an architecture test or analyzer (and `enforcement: test|analyzer` with an `enforcement_link`).
  • Checkable ADR rule enforced only by prose: DataView Design docs/design-docs/design_docs/qviews/data_view.md — ADR 'DataView Design' declares `enforcement: prose` but states a rule a test or analyzer can check: "The manager does not query SegmentMeta or infer state, level, visibility, importing, indexes, manifest versions, delete frontiers, or compaction lineage." Nothing in the build fails when the code breaks it — add an architecture test or analyzer (and `enforcement: test|analyzer` with an `enforcement_link`).
  • Checkable ADR rule enforced only by prose: WALSummary Design docs/design-docs/design_docs/wal/summary.md — ADR 'WALSummary Design' declares `enforcement: prose` but states a rule a test or analyzer can check: "Until this first publication succeeds, external checkpoint advancement must not depend on new chunks written under this term:" Nothing in the build fails when the code breaks it — add an architecture test or analyzer (and `enforcement: test|analyzer` with an `enforcement_link`).
  • Checkable ADR rule enforced only by prose: TransformLog Subscription Adaptor Design docs/design-docs/design_docs/wal/transform_log.md — ADR 'TransformLog Subscription Adaptor Design' declares `enforcement: prose` but states a rule a test or analyzer can check: "L0 materialization does not depend on this adaptor or on external subscribers." Nothing in the build fails when the code breaks it — add an architecture test or analyzer (and `enforcement: test|analyzer` with an `enforcement_link`).
D29 · Static Analysis (SAST) · REDACTED · ×5
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
X7 · Silent fallback defaults · Silent fallback default in catch · ×3
  • Silent fallback default in catch tools/mgit.py:214 — `get_commit_count_from_ref` swallows every exception into `return 0` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
  • Silent fallback default in catch tools/mgit.py:479 — `get_conflict_diff` swallows every exception into `return ''` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
  • Silent fallback default in catch tools/mgit.py:1498 — `get_release_branches` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
D20 · ADR Quality · ADR has no Consequences section · ×2
  • ADR has no Consequences section docs/design-docs/design_docs/20260413-search_embedded_agg.md:1 — docs/design-docs/design_docs/20260413-search_embedded_agg.md has no Consequences section (a heading such as `## Consequences`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Consequences section docs/design-docs/design_docs/20260720-segment-reopen-request-read-lease-drain-design.md:1 — docs/design-docs/design_docs/20260720-segment-reopen-request-read-lease-drain-design.md has no Consequences section (a heading such as `## Consequences`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
D16 · Bus Factor · Further sole-owners (lower concentration) · ×1
  • Further sole-owners (lower concentration) — 14 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 (89 single-owned of 1584 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; 1584 of the 2250 production source files in this repository met that bar). They are anonymized user #7 (2 file(s)), anonymized user #8 (2 file(s)), anonymized user #9 (2 file(s)), anonymized user #10 (2 file(s)), anonymized user #11 (1 file(s)), anonymized user #12 (1 file(s)) (+8 more) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: internal/util/arrowconv/arrow_to_fielddata.go, internal/datanode/compactor/stats.go, pkg/util/replicateutil/config_validator.go, pkg/metrics/cdc_metrics.go, pkg/util/paramtable/rbac_param.go, internal/metastore/streamingcoord_catalog.go, internal/parser/planparserv2/rewriter/array_contains.go, pkg/common/hash_routing_table.go (+10 more).
D20 · ADR Quality · ADR has no Context and Decision section · ×1
  • ADR has no Context and Decision section docs/design-docs/design_docs/20261005-arrow-retrieve-no-fielddata.md:1 — docs/design-docs/design_docs/20261005-arrow-retrieve-no-fielddata.md has no Context and Decision section (a heading such as `## Context`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
D34 · Knowledge Freshness · Further orphaned files (smaller) · ×1
  • Further orphaned files (smaller) — 64 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: pkg/mq/msgstream/msg_for_user_role.go, cmd/tools/migration/backend/etcd210.go, cmd/tools/migration/meta/210_to_220.go, pkg/util/typeutil/gen_empty_field_data.go, pkg/mq/msgstream/msg_for_collection.go, cmd/tools/migration/meta/meta220.go, cmd/tools/migration/meta/meta210.go, pkg/mq/msgstream/mqwrapper/kafka/kafka_consumer.go (and 56 more) (66 orphaned of 1585 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; 1585 of the 2250 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
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D40 · Network Egress Confinement · No network policy · ×1
  • No network policy — No Kubernetes NetworkPolicy (or Cilium policy) found. Without one, every pod can talk to every other pod and reach out to the internet by default. Add a default-deny policy and open only the flows you need.
D42 · Runtime Threat Enforcement · No runtime threat detection · ×1
  • No runtime threat detection — No runtime threat-detection engine (Tetragon TracingPolicy / Falco) is committed. These observe process, file and network activity in-kernel and can alert or kill on malicious behaviour a static scan cannot catch.
D42 · Runtime Threat Enforcement · No admission-control policy · ×1
  • No admission-control policy — No policy-enforcement gate (Kyverno / OPA Gatekeeper / PodSecurity admission) is committed. Admission control keeps workloads that violate your security baseline from ever reaching the cluster.
P2 · Observability · Logging is not universal · ×1
  • Logging is not universal — Only 5/7 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `cmd/tools/binlogv2`, `deployments/offline`.
P6 · Release Hygiene · No changelog · ×1
  • No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
X2 · Cancellation propagation · Not all functions that make a request accept a context.Context · ×1
  • Not all functions that make a request accept a context.Context — Only 8/9 functions that make a cancellable request (net/http, net.Dial) accept a context.Context or pass one on, so a request keeps running after whatever wanted it has given up — a cancelled request, a shutdown, an expired deadline. Take `ctx context.Context` as the first parameter and build the request with it (`http.NewRequestWithContext`, `DialContext`); where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
Minor — 114 finding(s)
D12 · Dependency Hygiene · Outdated · ×114
  • Outdated: cloud.google.com/go/storage — `cloud.google.com/go/storage` is required at v1.56.0 in REDACTED, but v1.70.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get cloud.google.com/go/storage@v1.70.0 && go mod tidy` and commit the updated REDACTED and go.sum.
  • Outdated: cloud.google.com/go/storage — `cloud.google.com/go/storage` is required at v1.56.0 in REDACTED, but v1.70.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get cloud.google.com/go/storage@v1.70.0 && go mod tidy` and commit the updated REDACTED and go.sum.
  • Outdated: github.com/Azure/azure-sdk-for-go/sdk/azcore — `github.com/Azure/azure-sdk-for-go/sdk/azcore` is required at v1.11.1 in REDACTED, but v1.23.3 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/Azure/azure-sdk-for-go/sdk/azcore@v1.23.3 && go mod tidy` and commit the updated REDACTED and go.sum.
  • Outdated: github.com/Azure/azure-sdk-for-go/sdk/azcore — `github.com/Azure/azure-sdk-for-go/sdk/azcore` is required at v1.11.1 in REDACTED, but v1.23.3 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/Azure/azure-sdk-for-go/sdk/azcore@v1.23.3 && go mod tidy` and commit the updated REDACTED and go.sum.
  • Outdated: github.com/Azure/azure-sdk-for-go/sdk/azidentity — `github.com/Azure/azure-sdk-for-go/sdk/azidentity` is required at v1.6.0 in REDACTED, but v1.15.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/Azure/azure-sdk-for-go/sdk/azidentity@v1.15.0 && go mod tidy` and commit the updated REDACTED and go.sum.
  • Outdated: github.com/Azure/azure-sdk-for-go/sdk/storage/azblob — `github.com/Azure/azure-sdk-for-go/sdk/storage/azblob` is required at v1.1.0 in REDACTED, but v1.8.2 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/Azure/azure-sdk-for-go/sdk/storage/azblob@v1.8.2 && go mod tidy` and commit the updated REDACTED and go.sum.
  • Outdated: github.com/Azure/azure-sdk-for-go/sdk/storage/azblob — `github.com/Azure/azure-sdk-for-go/sdk/storage/azblob` is required at v1.1.0 in REDACTED, but v1.8.2 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/Azure/azure-sdk-for-go/sdk/storage/azblob@v1.8.2 && go mod tidy` and commit the updated REDACTED and go.sum.
  • Outdated: github.com/RoaringBitmap/roaring/v2 — `github.com/RoaringBitmap/roaring/v2` is required at v2.8.0 in REDACTED, but v2.30.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/RoaringBitmap/roaring/v2@v2.30.0 && go mod tidy` and commit the updated REDACTED and go.sum.
  • Outdated: github.com/RoaringBitmap/roaring/v2 — `github.com/RoaringBitmap/roaring/v2` is required at v2.8.0 in REDACTED, but v2.30.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/RoaringBitmap/roaring/v2@v2.30.0 && go mod tidy` and commit the updated REDACTED and go.sum.
  • Outdated: github.com/RoaringBitmap/roaring/v2 — `github.com/RoaringBitmap/roaring/v2` is required at v2.8.0 in REDACTED, but v2.30.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/RoaringBitmap/roaring/v2@v2.30.0 && go mod tidy` and commit the updated REDACTED and go.sum.
  • Outdated: github.com/aliyun/credentials-go — `github.com/aliyun/credentials-go` is required at v1.2.7 in REDACTED, but v1.4.13 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/aliyun/credentials-go@v1.4.13 && go mod tidy` and commit the updated REDACTED and go.sum.
  • Outdated: github.com/apache/pulsar-client-go — `github.com/apache/pulsar-client-go` is required at v0.19.0 in REDACTED, but v0.21.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/apache/pulsar-client-go@v0.21.0 && go mod tidy` and commit the updated REDACTED and go.sum.
  • Outdated: github.com/apache/pulsar-client-go — `github.com/apache/pulsar-client-go` is required at v0.19.0 in REDACTED, but v0.21.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/apache/pulsar-client-go@v0.21.0 && go mod tidy` and commit the updated REDACTED and go.sum.
  • Outdated: github.com/aws/aws-sdk-go-v2 — `github.com/aws/aws-sdk-go-v2` is required at v1.41.5 in REDACTED, but v1.47.4 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/aws/aws-sdk-go-v2@v1.47.4 && go mod tidy` and commit the updated REDACTED and go.sum.
  • Outdated: github.com/aws/aws-sdk-go-v2/config — `github.com/aws/aws-sdk-go-v2/config` is required at v1.29.9 in REDACTED, but v1.33.10 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/aws/aws-sdk-go-v2/config@v1.33.10 && go mod tidy` and commit the updated REDACTED and go.sum.
  • Outdated: github.com/aws/aws-sdk-go-v2/credentials — `github.com/aws/aws-sdk-go-v2/credentials` is required at v1.17.62 in REDACTED, but v1.20.10 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/aws/aws-sdk-go-v2/credentials@v1.20.10 && go mod tidy` and commit the updated REDACTED and go.sum.
  • Outdated: github.com/aws/aws-sdk-go-v2/service/bedrockruntime — `github.com/aws/aws-sdk-go-v2/service/bedrockruntime` is required at v1.50.4 in REDACTED, but v1.63.7 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/aws/aws-sdk-go-v2/service/bedrockruntime@v1.63.7 && go mod tidy` and commit the updated REDACTED and go.sum.
  • Outdated: github.com/bits-and-blooms/bitset — `github.com/bits-and-blooms/bitset` is required at v1.12.0 in REDACTED, but v1.26.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/bits-and-blooms/bitset@v1.26.0 && go mod tidy` and commit the updated REDACTED and go.sum.
  • Outdated: github.com/bits-and-blooms/bloom/v3 — `github.com/bits-and-blooms/bloom/v3` is required at v3.3.1 in REDACTED, but v3.7.1 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/bits-and-blooms/bloom/v3@v3.7.1 && go mod tidy` and commit the updated REDACTED and go.sum.
  • Outdated: github.com/bytedance/mockey — `github.com/bytedance/mockey` is required at v1.4.6 in REDACTED, but v1.4.8 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/bytedance/mockey@v1.4.8 && go mod tidy` and commit the updated REDACTED and go.sum.
  • Outdated: github.com/bytedance/mockey — `github.com/bytedance/mockey` is required at v1.4.6 in REDACTED, but v1.4.8 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/bytedance/mockey@v1.4.8 && go mod tidy` and commit the updated REDACTED and go.sum.
  • Outdated: github.com/bytedance/mockey — `github.com/bytedance/mockey` is required at v1.4.6 in REDACTED, but v1.4.8 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/bytedance/mockey@v1.4.8 && go mod tidy` and commit the updated REDACTED and go.sum.
  • Outdated: github.com/bytedance/sonic — `github.com/bytedance/sonic` is required at v1.15.2 in REDACTED, but v1.15.4 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/bytedance/sonic@v1.15.4 && go mod tidy` and commit the updated REDACTED and go.sum.
  • Outdated: github.com/casbin/json-adapter/v2 — `github.com/casbin/json-adapter/v2` is required at v2.0.0 in REDACTED, but v2.1.1 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/casbin/json-adapter/v2@v2.1.1 && go mod tidy` and commit the updated REDACTED and go.sum.
  • Outdated: github.com/cenkalti/backoff/v4 — `github.com/cenkalti/backoff/v4` is required at v4.2.1 in REDACTED, but v4.3.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/cenkalti/backoff/v4@v4.3.0 && go mod tidy` and commit the updated REDACTED and go.sum.
  • + 89 more in this group — see findings.md.

Appendix B — Reproduction & audit trail

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

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-e4328ce2eea1428fb9987e407d33a44c/history.json --exit-code 0 --source .2artifacts/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-e4328ce2eea1428fb9987e407d33a44c/tree.json --exit-code 0 --source .2artifacts/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 .743artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-a86050eb55d94a57858400eb05c5582531artifacts/raw/osv-scanner.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .253artifacts/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 29 file(s) — `client/column/array.go`, `client/column/columns.go`, `client/column/geometry.go`, `client/column/json.go`, `client/column/scalar.go`, … (+24 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.0—
D37 · Vulnerability-disclosure Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.0—
D43 · Malicious Dependenciesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-a86050eb55d94a57858400eb05c558250artifacts/raw/osv-scanner.json

Run 01a16bcf-81f3-7fa0-a3a1-9cabcaccfebb · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Issues: 272 · Warnings: 871 · Recommendations: 803 · Info: 114 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 24-10-2026 @ 02:48 UTC.

Downloadable artifacts

Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.

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